On this page (7 sections)

A critical flaw tracked as CVE-2026-126173 affects the webhook addon of the AutomatorWP Pro plugin for WordPress in all versions up to and including 1.4.4. According to the GitHub Advisory Database entry, an unauthenticated attacker can reset the password of any WordPress account, including administrators, which amounts to full account takeover.

The flaw is only reachable when an administrator has built one specific automation. If you run AutomatorWP Pro with the webhook addon, review your automations now, because the risky setup is a documented and supported configuration, not a misconfiguration most people would think of as unusual.

What happened

The advisory was published on November 14, 2026, and the NVD record carries the same description. The NVD entry repeats the advisory text, so it is not independent confirmation. The advisory is also marked as unreviewed by GitHub, and the research lists a Wordfence threat intelligence page as a reference but gives no further detail from it. Treat the details below as coming from a single description.

The cause is missing authorization (CWE-862): the plugin does not properly verify that the caller is allowed to perform the action. In plain terms, a request that should have been checked is accepted from anyone who can reach the webhook, and the action it triggers is a password change.

When is a site actually exposed?

The advisory says the issue is exploitable only when an administrator has configured an automation with all of the following parts:

  • A Receive Webhook trigger that includes an 'Is the user ID' field.
  • An Update-User action wired to that trigger.
  • The Update-User action's User ID field left blank.
  • The action's Password field mapped to the webhook password tag.

If you have no automation that matches this combination, the advisory indicates the attack path is not available. That said, the vulnerable code is in versions up to 1.4.4, so a future configuration change could create the exposure. The CVSS vector reflects the worst case where the setup exists: network attack, low complexity, no privileges and no user interaction.

Why this matters

An administrator password reset gives an attacker the keys to the site. From there, attackers typically install plugins or edit theme files to run their own code, create hidden admin users or access customer data. The sources do not report any exploitation of this specific flaw, but a critical, unauthenticated issue in a popular plugin category tends to attract scanning soon after publication, so acting early is sensible.

How to check your site

First confirm whether the plugin is installed and which version it is. If you have WP-CLI access, this read-only command lists plugins matching the name, with their status and version. Look for any AutomatorWP entry at 1.4.4 or lower.

List AutomatorWP plugins with status and version (run from the WordPress root)WP-CLI
wp plugin list --fields=name,status,version | grep -i automatorwp

Then inspect your automations in the WordPress admin under AutomatorWP. For each automation that uses a Receive Webhook trigger, look at the actions. Pay particular attention to any Update-User action where the User ID is empty and the Password field uses the webhook password tag.

Finally, look for signs that something already happened: unexpected password reset emails, administrators who suddenly cannot log in, new administrator accounts, or recent changes to users you did not make. Check your web server logs for unusual POST requests to the webhook endpoints around or after the publication date.

What to do now

The advisory does not name a patched version, so do not assume that updating alone resolves the issue. Check the vendor site at automatorwp.com and the Wordfence entry for fix information, and apply any release newer than 1.4.4 once the vendor confirms it addresses this CVE.

  1. Identify every site that uses AutomatorWP Pro and note whether the webhook addon is active.
  2. Find automations that pair a Receive Webhook trigger with an Update-User action whose User ID is blank and whose Password field uses the webhook password tag.
  3. Disable or delete those automations until a fixed version is confirmed. If the addon is not needed, deactivate it.
  4. Check the vendor and Wordfence pages for a patched release, then update and re-test your automations.
  5. Review the Users list for unknown administrators and confirm all admin accounts are yours.
  6. If you suspect misuse, reset passwords for administrator accounts, invalidate sessions and rotate any API keys stored on the site.
  7. Enable two-factor authentication for administrators so a reset password alone is not enough to log in.
Caution. Disabling an automation or the webhook addon will stop any workflow that depends on it, such as user syncs from external systems. Check what relies on the webhook before turning it off, and tell the owners of those integrations.
Tip. If you cannot update yet, a website firewall that restricts access to the webhook URL to known source IPs can reduce exposure, but it is a stopgap and not a substitute for removing the risky automation. See what a WAF is for what these tools can and cannot do.

Detection and monitoring afterwards

Keep an eye on administrator accounts and login activity for several weeks. Alert on new users with elevated roles, password changes you did not request and logins from unfamiliar locations. Our guide on checking whether a website is hacked covers the signs to look for, and what to do if your website is hacked explains recovery.

It also helps to track plugin vulnerabilities over time. The WordPress plugin vulnerability pages and the WordPress security checklist are good starting points for a routine review of what is installed on your sites.

What remains unknown

  • The first fixed version is not stated in the sources.
  • The advisory is marked unreviewed by GitHub and no package is listed, so automated dependency alerts will not flag it.
  • No exploitation reports appear in the research, and only one underlying description of the flaw is available.
  • Exact webhook endpoint paths and request formats are not described, so log searches should be broad.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-126173 - GitHub Advisory Databasegithub.com
  2. CVE-2026-126173: The AutomatorWP Pro plugin for WordPress' webhook addon is vulnerable to authorization bypass in all versions up to, and including, 1.4.4.nvd.nist.gov ·
  • WordPress
  • AutomatorWP
  • CVE-2026-126173
  • Authorization bypass
  • Account takeover