AutomatorWP Pro Plugin up to 1.4.4 on WordPress authorization

Summaryinfo

A vulnerability categorized as critical has been discovered in AutomatorWP Pro Plugin up to 1.4.4. This vulnerability affects unknown code. Such manipulation leads to authorization. This vulnerability is documented as CVE-2026-126173. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in AutomatorWP Pro Plugin up to 1.4.4 and classified as critical. Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality, integrity, and availability. CVE summarizes:

The AutomatorWP Pro plugin for WordPress' webhook addon is vulnerable to authorization bypass in all versions up to, and including, 1.4.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to reset the password of any WordPress account, including administrators, resulting in full account takeover. This is only exploitable when an administrator has configured an automation pairing 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, which is a documented, supported plugin configuration.

The advisory is shared for download at wordfence.com. This vulnerability is handled as CVE-2026-126173 since 11/10/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/14/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• AutomatorWP

Name

• Pro Plugin

Version

• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion