Critical PHP2Shell: two unauthenticated RCE flaws in PHP itself. Fixes shipped on 21 Oct 2026. Check if you are affected →
← All news

AutomatorWP Webhooks Add-on ≤ 1.4.4 Lets Unauthenticated Callers Reset Any Password, Including Admins' (CVE-2026-126173)

Wordfence disclosed CVE-2026-126173 (CVSS 9.8) on November 13, 2026: a missing authorization check in the AutomatorWP Pro Webhooks add-on lets an anonymous request reset any WordPress account's password when a common Receive Webhook to Update User automation is set up. Version 1.4.5 fixes it.

Wordfence published CVE-2026-126173 on November 13, 2026, a critical flaw (CVSS 3.1 score 9.8) in the Webhooks add-on for AutomatorWP Pro, the no-code automation plugin for WordPress. All add-on versions up to and including 1.4.4 are affected; 1.4.5 is the patched release. The issue was reported by researcher 0xd4rk5id3 (EnvoraSec).

What goes wrong

According to Wordfence, the add-on does not properly verify that the caller is authorized to perform the action a webhook triggers. An unauthenticated attacker can therefore reset the password of any WordPress account, administrators included, and take the site over.

It is not exploitable on every install. The site needs an automation that pairs:

  • a Receive Webhook trigger that uses an "Is the user ID" field, with
  • an Update User action whose User ID field is left blank and whose Password field is mapped to the webhook's password tag.

Wordfence stresses that this is a documented, supported configuration, not an exotic misuse. Sites that use incoming webhooks to sync accounts from a CRM, LMS or membership system are exactly the ones likely to have built it.

What to do

  1. Update the AutomatorWP Webhooks add-on to 1.4.5 or later. It is a Pro add-on, so it may not update through the normal WordPress.org channel; check that your license is active and the update actually landed.
  2. Keep AutomatorWP core current too. The core plugin has had its own recent fixes, including a missing authorization issue patched in 6.0.7 and a CSRF issue (CVE-2026-121472) patched in 6.0.8.
  3. Review your automations. List every Receive Webhook trigger connected to an Update User action, and ask whether an outside system really needs to set passwords. If not, remove that mapping.
  4. Look for signs of abuse. Check for unexpected password changes, new or unfamiliar administrator accounts, and webhook requests in your access logs from sources you don't recognise. If anything looks wrong, rotate admin passwords and invalidate sessions.

The bigger pattern

Webhook receivers are public endpoints by design. Whenever a plugin lets inbound data drive privileged actions such as creating users, changing roles or setting passwords, authorization has to be checked on the action, not assumed from the trigger. This is the same class of bug behind many of this year's WordPress account-takeover CVEs.


Running an older WordPress stack with plugins you can't easily update, or an automation setup nobody fully remembers? RescuePHP can audit integrations like this, patch or backport fixes on legacy PHP and WordPress versions, and help you clean up after a suspected takeover.