The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-126173: AutomatorWP flaw risks admin takeover

By The Daily Byte ·14 Nov 2026 ·4 min read
The WordPress admin dashboard, the platform affected by the AutomatorWP Pro vulnerability

A critical vulnerability in the AutomatorWP Pro plugin for WordPress could let an unauthenticated attacker reset the password of any account on an affected site, including administrators, leading to a full account takeover. The flaw, tracked as CVE-2026-126173, was published on 14 November 2026 with a CVSS severity score of 9.8 out of 10, the highest band of the scoring scale.

The vulnerability is an authorisation bypass in the plugin's webhook addon, affecting all versions up to and including 1.4.4. It exists because the plugin does not properly verify that a user is authorised to perform an action, so an attacker on the internet can invoke privileged functionality directly, with no login and no interaction from a victim required.

When is a site at risk?

The flaw is only exploitable when a site administrator has configured a specific automation. That automation pairs a Receive Webhook trigger, with an "Is the user ID" field, to an Update-User action whose User ID field is left blank and whose Password field is mapped to the webhook password tag. This is a documented, supported plugin configuration, which is what makes the issue so serious for sites that use it: nothing unusual or unsupported is needed to trigger it.

Sites running AutomatorWP Pro that have not set up this particular automation pairing are not exposed through this route. The distinction matters, because the first step for any site owner is to check whether the vulnerable pattern exists in their own automations, rather than assuming every installation is equally at risk.

How bad is the flaw?

The CVSS vector for the vulnerability is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms, the attack works over the network, takes little complexity, needs no privileges and no user interaction, and can cause a high loss of confidentiality, integrity and availability. An attacker who resets an administrator's password gains the keys to the whole site: they can change content, install plugins, create accounts and lock the rightful owners out.

The weakness is classified as CWE-862, missing authorisation. It is a design-level problem in how the webhook addon handles incoming requests, rather than a single mistyped check, which is why administrators should treat the affected configuration as unsafe until it is changed or the plugin is updated.

What is known so far

The CVE record was reserved on 10 November and published on 14 November, with Wordfence as the assigning CNA. The record has not yet been added to the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalogue, and it has no exploit-prediction score yet. No public proof-of-concept exploit code is listed for the flaw, and no exploitation in the wild has been reported at the time of writing. That is reassuring, but it is an absence of evidence rather than proof that attacks will not follow, and critical WordPress flaws are routinely probed once they become public.

WordPress powers a large share of the web, and automation plugins such as AutomatorWP are widely used to connect forms, membership tools, shops and mailing lists. A flaw that turns a webhook into an administrator password reset is therefore a significant risk for the sites that have the vulnerable automation switched on, even though only a subset of installations is affected.

What site owners should do

Site owners running AutomatorWP Pro should first review their automations for the risky pattern: a Receive Webhook trigger using the "Is the user ID" field, connected to an Update-User action with a blank User ID and a password mapped from the webhook. If that automation exists, it should be disabled or reworked so that password changes cannot be triggered by an unauthenticated webhook call.

Owners should also check for an updated release from AutomatorWP and apply it as soon as one is available, and review administrator accounts for unfamiliar users, recent password changes or unexpected activity. Any account that looks suspicious should have its password reset from a trusted system and its sessions revoked. Until the automation is fixed, the safest course is to treat any webhook that can touch user accounts as a privileged endpoint, and to make sure it cannot be reached by strangers.