AutomatorWP Pro Webhooks ≤ 1.4.4: An Unauthenticated Webhook Can Reset Any Password (CVE-2026-126173, CVSS 9.8)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

AutomatorWP Pro Webhooks ≤ 1.4.4: An Unauthenticated Webhook Can Reset Any Password (CVE-2026-126173, CVSS 9.8)

A webhook receiver that never checks who is allowed to act on it is an open door — and when the automation behind it can update user passwords, that door leads straight to the administrator account. That is CVE-2026-126173 in the Webhooks addon for AutomatorWP Pro: a missing authorization check makes it possible for an unauthenticated attacker to reset the password of any WordPress account, including administrators, resulting in full account takeover, at CVSS 9.8. A public proof of concept appeared the day after the record was published.

What Happened

CVE-2026-126173 is a missing authorization vulnerability (CWE-862) in the AutomatorWP Pro Webhooks addon for WordPress, disclosed November 13, 2026 (CNA: Wordfence; the CVE record was published November 14, 2026).

Am I Affected?

Check wp-admin → AutomatorWP → Automations. You are in the affected set if both of these hold: the Webhooks addon is at 1.4.4 or below, and one of your automations pairs a Receive Webhook trigger (with an 'Is the user ID' field) to an Update-User action with a blank User ID field and the Password field mapped to the webhook password tag.

One honesty note, because it is the whole point of how we cover these: we can't version-check this one. The Webhooks addon is a premium AutomatorWP Pro addon with no wordpress.org listing and no verified public readme slug for the addon itself, so there is no public version announcement for a passive scan to read — and keying a check to the free core plugin's version line would be guessing, because that is a different product with its own versioning. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Update AutomatorWP Pro, including the Webhooks addon, to the newest available release today.
  2. Until you have updated, disable or reconfigure any automation matching the vulnerable pattern. Setting the Update-User action's User ID explicitly, or unmapping the Password field from the webhook tag, closes the reachable path described in the CVE record.
  3. Audit administrator accounts and recent password resets. This flaw's residue is a legitimate account with an attacker-chosen password — every Administrator should be a person you can name, and any password reset you cannot explain deserves an immediate reset of your own and a session review.

The Bigger Lesson

A webhook endpoint is an unauthenticated input surface by design: anyone on the internet can call it. Every action a webhook can trigger inherits that exposure unless the handler verifies authorization itself. Automations that touch identity — password changes above all — must never trust that the caller was entitled to ask. If a no-code automation tool can change a password, its trigger surface deserves the same review you would give a login form.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the account audit finds a stranger.


Running AutomatorWP Pro on a WordPress site? Update today, check your webhook automations against the pattern above, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report