Skip to main content
VulnerabilityPublished

CVE-2026-126173: AutomatorWP Webhooks (WordPress plugin) · Missing Authorization

Affects AutomatorWP Webhooks (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical · fixed in 1.4.4 : patch AutomatorWP Webhooks (WordPress plugin) as a priority.

Data as of 14 Nov 2026, 05:04 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.19.8
Patch
Available – fixed in 1.4.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
AutomatorWPAutomatorWP WebhooksAffected
  • <=1.4.4
Fixed in–

AI-suggested

A fix is available in versions later than 1.4.4. Users should upgrade AutomatorWP Pro plugin's webhook addon to a version newer than 1.4.4 to remediate this vulnerability. Until patched, avoid configuring automations that pair a Receive Webhook trigger with an Update-User action as described, or restrict webhook access to trusted sources only.

Description

A critical authorization bypass vulnerability exists in the AutomatorWP Pro plugin for WordPress, specifically in the webhook addon, affecting all versions up to and including 1.4.4. This flaw allows unauthenticated attackers to reset passwords of any WordPress user account, including administrators, leading to full account takeover. Exploitation requires a specific plugin configuration involving a Receive Webhook trigger paired with an Update-User action with certain fields left blank or mapped to the webhook password tag.

References

Community reviews

Loading reviews…