CVE-2026-126173: Patch AutomatorWP Webhooks to 1.4.5
Update the AutomatorWP Pro Webhooks add-on to 1.4.5 or a newer patched version if you run 1.4.4 or earlier. Wordfence’s advisory lists the flaw as patched and identifies 1.4.5 as the remediation version.
Wordfence, the assigning CNA, rates CVE-2026-126173 Critical at CVSS 3.1 9.8. Its CNA record records disclosure on November 13, 2026 at 15:42:28 UTC and CVE publication on November 14 at 04:46:10.057 UTC. Neither source establishes active exploitation.
Check the automation configuration
According to the CNA, an unauthenticated attacker can reset any WordPress account’s password, including an administrator’s, when an administrator has configured both parts of this automation:
- A Receive Webhook trigger has an
Is the user IDfield. - Its paired Update-User action leaves
User IDblank and mapsPasswordto the webhook password tag.
The missing authorization check allows this configured path to change another user’s password, leading to account takeover. The CNA calls this a documented, supported configuration; it does not say that every installation enables it. Review the saved automation settings without sending a password-reset request.
Install and verify the update
Record the installed Webhooks add-on version and the automations that use it. Back up the site using your normal recovery procedure, then obtain the update through the vendor’s supported channel. Verify the Webhooks add-on’s own version after installation; updates to WordPress, other AutomatorWP components or Linux alone do not establish that it is patched.
If an immediate update is not possible, consider temporarily disabling the affected automation with its owner after checking which business process depends on it. That is a containment recommendation based on the reported prerequisite, not a tested vendor workaround. Keep the update scheduled.
Afterward, confirm that the add-on reports 1.4.5 or a newer patched version and retain the installation record. Check ordinary authorized workflows using your normal test accounts and procedure. Do not test the flaw by trying to reset a production account’s password.
Read the advisory metadata from Linux
Download a pinned public CNA record and inspect it locally with Bash, curl and Python 3. These commands make no request to a WordPress site. Keep the same terminal session for setup, execution and cleanup, starting with a scratch directory. Stop if directory creation or changing into it fails; do not save files or run the later blocks.
advisory_dir=$(mktemp -d ./automatorwp-advisory.XXXXXX) &&
cd -- "$advisory_dir"Save this helper as inspect-automatorwp-advisory.py inside that directory:
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
if record["cveMetadata"]["cveId"] != "CVE-2026-126173":
raise SystemExit("Unexpected CVE ID")
cna = record["containers"]["cna"]
disclosed = next(item["time"] for item in cna["timeline"] if item["value"] == "Disclosed")
print("Disclosed:", disclosed)
print("CVE record published:", record["cveMetadata"]["datePublished"])
for product in cna["affected"]:
print("Product:", product["product"])
for version in product["versions"]:
if version["status"] == "affected":
print("Affected through (inclusive):", version["lessThanOrEqual"])
score = cna["metrics"][0]["cvssV3_1"]
print(f"CVSS {score['version']}: {score['baseScore']} {score['baseSeverity']}")
print("Advisory metadata only; no installed software was inspected.")Download the record and run the helper:
curl --fail --silent --show-error 'https://raw.githubusercontent.com/CVEProject/cvelistV5/5c76448e1e5a5f996f7dfcabb677a7f963afb46b/cves/2026/126xxx/CVE-2026-126173.json' --output automatorwp-cve.json &&
python3 inspect-automatorwp-advisory.py automatorwp-cve.jsonActual output on Debian 13 with Python 3.12.14:
Disclosed: 2026-11-13T15:42:28.000Z
CVE record published: 2026-11-14T04:46:10.057Z
Product: AutomatorWP Webhooks
Affected through (inclusive): 1.4.4
CVSS 3.1: 9.8 CRITICAL
Advisory metadata only; no installed software was inspected.This output is a reference for inventory work. It does not read your installed version or automation settings, and it cannot verify the runtime fix. The fixed version comes from Wordfence’s advisory; the pinned JSON contains the affected range. Remove only the two example files and their scratch directory when finished:
rm -- inspect-automatorwp-advisory.py automatorwp-cve.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dirIf account activity raises concern, preserve available access and automation logs and investigate unexpected password changes or administrator activity through your incident-response process. These are investigation leads, not indicators that prove exploitation of this CVE. Installing the update does not resolve an account takeover that already occurred.
Only the public-record download and local parser were executed for this article. No AutomatorWP installation, patch behavior or password-reset path was tested.
This post was created with assistance from AI.