WPDeeply
Download free plugin
Plugin Security

AutomatorWP Pro Webhooks

AutomatorWP Pro Webhooks through 1.4.4 has an actively exploited unauthenticated password-reset flaw that can lead to administrator account takeover. Update to 1.4.5 or later.

AutomatorWP logo for the CVE-2026-126173 Webhooks account takeover advisory

AutomatorWP Pro Webhooks versions through 1.4.4 are vulnerable to an unauthenticated password-reset and account-takeover flaw tracked as CVE-2026-126173. Patchstack lists the issue as known to be exploited. Sites using the affected webhook automation pattern should update to version 1.4.5 or later immediately.

Vulnerability summary

  • Product: AutomatorWP Pro Webhooks add-on
  • Affected versions: 1.4.4 and earlier
  • Fixed version: 1.4.5
  • CVE: CVE-2026-126173
  • Class: Missing authorization leading to arbitrary user password reset and account takeover
  • Severity: CVSS 9.8 Critical
  • Required privilege: None
  • User interaction: None
  • Exploitation status: Listed by Patchstack as known to be exploited; this is Patchstack telemetry, not a CISA Known Exploited Vulnerabilities catalog designation

Exploit prerequisites

The vulnerable add-on is not described as exploitable under every AutomatorWP configuration. The CVE record identifies a specific, supported automation pattern:

  • A Receive Webhook trigger includes an Is the user ID field.
  • The trigger is paired with an Update User action.
  • The Update User action leaves its User ID field blank.
  • The Password field is mapped to the password value received by the webhook.

When that pattern exists, affected versions do not adequately verify that the unauthenticated requester is authorized to change the targeted account. An attacker can reset the password of an arbitrary WordPress user, including an administrator, and then sign in as that account.

This advisory intentionally omits request templates, webhook payloads, and other material that would enable abuse.

Potential impact

Successful exploitation can give an attacker full control of a privileged WordPress account. From an administrator session, the attacker may install or alter plugins and themes, create persistent users, access private content and customer data, change site settings, or deploy additional malware.

A password reset may also lock the legitimate account owner out. Treat unexpected password changes or administrator logins as a possible incident, not only as a credential problem.

Immediate mitigation

  1. Update AutomatorWP Pro Webhooks to version 1.4.5 or later.
  2. Review Receive Webhook automations for the affected Is the user ID and Update User mapping.
  3. If the update cannot be completed immediately, disable the affected automation or deactivate the Webhooks add-on until a patched release is installed.
  4. Restrict webhook endpoints at the reverse proxy or WAF when they are not intended to receive public traffic.
  5. Review AutomatorWP execution logs, authentication logs, password-reset activity, and administrator accounts for unauthorized changes.
  6. If compromise is suspected, preserve logs before rotating administrator passwords, WordPress salts, API credentials, and other secrets available to WordPress.

Verify the installed version

Premium add-on directory names can differ by package, so first list the installed plugins and identify the exact AutomatorWP Webhooks entry:

wp plugin list --fields=name,status,version,update
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered

Confirm that the Webhooks add-on reports version 1.4.5 or newer. Also check deployment manifests, Composer packages, managed-plugin policies, and backup restoration procedures so an older vulnerable package is not reintroduced.

Investigation guidance

No universal malicious IP address, domain, or file hash has been published for CVE-2026-126173. Useful behavioral indicators include:

  • Unexpected password-reset events for administrator or editor accounts
  • Successful logins from unfamiliar addresses or devices immediately after a password change
  • Unrecognized executions of Receive Webhook automations
  • New administrator accounts, application passwords, or scheduled tasks
  • Unexpected plugin, theme, option, or user-role changes
  • New or recently modified PHP files in writable WordPress directories

Useful defensive checks include:

wp user list --fields=ID,user_login,user_email,roles,user_registered
wp plugin list --status=active --fields=name,status,version,update
wp cron event list --fields=hook,next_run_gmt,recurrence
wp core verify-checksums

Compare the output with the approved account and deployment inventory. Review the site access log, security-plugin events, AutomatorWP logs, mail logs for password-reset messages, and hosting control-panel authentication history for the disclosure and exploitation window.

Remediation checklist

  • Update AutomatorWP Pro Webhooks to 1.4.5 or later.
  • Audit Receive Webhook and Update User mappings for the vulnerable configuration.
  • Review password changes, logins, privileged users, application passwords, plugins, themes, and cron events.
  • Remove unauthorized persistence only after preserving evidence.
  • Rotate passwords, salts, and exposed secrets if account takeover may have occurred.
  • Test legitimate webhook automations after the update and cache purge.

Sources

WPdeeply

WPDeeply is the site's editorial account for WordPress security advisories, plugin risk research, and remediation guides. Articles under this byline are checked against vendor changelogs, CVE records, vulnerability database entries, and the WPDeeply editorial policy before publication.