Security notice
Use the AutomatorWP Pro Webhooks add-on? Someone without a login could take over accounts. Update to 1.4.5 or later today.
The AutomatorWP Pro Webhooks add-on for WordPress has CVE-2026-126173 in versions 1.4.4 and earlier. It lets someone without a login reset account passwords, including administrator passwords, and take over those accounts. This is a paid add-on, not the AutomatorWP plugin by itself. Wordfence says it is exploitable when a webhook automation that can change a user's password is in use. Patchstack rates it CVSS 9.8 (critical). Wordfence also rates it 9.8. Patchstack marks it as known to be exploited. Patchstack published its entry on November 13, 2026. The fix is version 1.4.5. This is a premium add-on, so check that your license is active and the update actually arrived. If you use this add-on, update to 1.4.5 or later today. If you cannot update, deactivate the add-on until you can. (Patchstack, Nov 13, Wordfence)
What happened
- The flaw. CVE-2026-126173 affects the AutomatorWP Pro Webhooks add-on for WordPress in versions 1.4.4 and earlier. Someone without a login can reset the password of a WordPress account, including an administrator account, and take it over. This is a paid add-on, not the AutomatorWP plugin by itself. Wordfence says the flaw is exploitable when a webhook automation that can change a user's password is in use, and that this is a documented, supported setup. (Patchstack, Wordfence)
- Known to be exploited, per Patchstack. Patchstack marks this vulnerability as known to be exploited. That is Patchstack's own assessment. (Patchstack)
- Severity. Patchstack rates it CVSS 9.8 (critical). Wordfence also rates it 9.8 (critical). (Patchstack, Wordfence)
- The fix. Patchstack and Wordfence identify 1.4.5 as the first fixed version. Update to 1.4.5 or later. We could not find a public AutomatorWP changelog page that lists the 1.4.5 fix in its own words. (Patchstack, Wordfence)
Who should worry
Any WordPress site running the AutomatorWP Pro Webhooks add-on 1.4.4 or earlier. This is a paid add-on, not the free or core AutomatorWP plugin by itself. If you do not use this add-on, this notice does not apply to you.
What to do now
- Update the AutomatorWP Pro Webhooks add-on to 1.4.5 or later today. Back up the site first. This is a premium add-on, so confirm your license is active, then in WordPress admin go to Plugins, Installed Plugins, and confirm the installed version even if automatic updates are enabled or your host manages updates. (Patchstack, Wordfence)
- If the update has to wait, deactivate the add-on until you can install the fixed version. You can also turn off webhook automations that change account passwords until the update is in place.
- Check for signs of tampering. Look for unexpected password resets, new or unfamiliar administrator accounts, and odd logins or settings. Updating closes the flaw; it does not undo access an attacker may already have gained.
- If you find signs of a break-in, change passwords, tell affected users, and ask your developer or host to investigate.
What to send your developer, agency or host
Please check whether our WordPress site runs the AutomatorWP Pro Webhooks add-on (a premium add-on, not the AutomatorWP plugin alone). CVE-2026-126173 affects versions 1.4.4 and earlier; unauthenticated attackers can reset account passwords and take over accounts, fixed in 1.4.5. Patchstack and Wordfence rate it 9.8. Patchstack marks it as known to be exploited. Please update us to 1.4.5 or later today, or deactivate the add-on until the update can be installed, then check for unexpected password resets, accounts or logins, and confirm the version you left us on. Sources: Patchstack, Wordfence, NVD.
Common questions
Does this mean my site was hacked?
No. A vulnerable version is a reason to update and review the site, not proof of a break-in. Patchstack marks this flaw as known to be exploited, so do not wait.
Can EverThread tell me if I am affected?
No. EverThread does not test for this. We cannot see which WordPress plugins or add-ons your site runs or which versions they are on. A scan without a warning about this add-on does not mean your site is safe.
Which version should I install?
1.4.5 is the first version that fixes this flaw. Install 1.4.5 or later. You need an active AutomatorWP Pro Webhooks license to receive the update. (Patchstack, Wordfence)
Does this affect every AutomatorWP site?
No. The flaw is in the paid Webhooks add-on, not in AutomatorWP itself. Wordfence says it is exploitable when a webhook automation that can change a user's password is in use. If you are not sure whether you have that setup, update the add-on anyway.
Where can I follow updates?
Follow Patchstack, Wordfence, the NVD entry and the AutomatorWP Webhooks add-on page. All current notices are on our notices page.
Security alerts by email
Hear about the next one first.
When a flaw puts websites at risk, we send one email: what happened, who it affects and what to do. It's free, whether or not you use EverThread.
Sources
- Patchstack database, CVE-2026-126173: published November 13, 2026. AutomatorWP Pro Webhooks add-on versions 1.4.4 and earlier. Patched in 1.4.5. Rated 9.8. Required privilege: unauthenticated. Marked known to be exploited.
- Wordfence threat intelligence, CVE-2026-126173: publicly published November 13, 2026. CVSS 9.8 (critical). Unauthenticated password reset and account takeover in the Pro Webhooks add-on through 1.4.4, fixed in 1.4.5. Wordfence says this is exploitable when a webhook automation that can change a user's password is in use, and that this is a documented, supported setup.
- NVD CVE-2026-126173: CVE record for this vulnerability.
- AutomatorWP Webhooks add-on page: vendor product page for the paid Webhooks add-on. We could not find a public AutomatorWP changelog entry that describes the 1.4.5 fix in the vendor's own words. The AutomatorWP /changelog/ URL returned a "Page not found" response when checked on November 16, 2026.
- WP Server Guard, November 2026 plugin briefing: last reviewed November 16, 2026. Lists AutomatorWP Pro Webhooks CVE-2026-126173, citing Patchstack's known-to-be-exploited marker, versions through 1.4.4, fix 1.4.5, CVSS 9.8, published November 13.