CVE-2026-126173 in Pro Plugininfo

Summary

by MITRE • 11/14/2026

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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/14/2026

The AutomatorWP Pro WordPress plugin contains a critical authorization bypass vulnerability in its webhook addon affecting all versions up to 1.4.4. This flaw stems from insufficient verification of user privileges when processing incoming webhook requests. The core issue lies in the logic governing how the plugin handles actions triggered by webhooks, specifically regarding identity management and permission checks. When an administrator configures an automation that pairs a Receive Webhook trigger with an Update-User action, the system fails to adequately validate whether the source of the request has the necessary permissions to modify user accounts. This lack of rigorous authorization checking allows unauthenticated attackers to interact directly with these webhook endpoints without valid session tokens or API keys typically required for such operations.

The technical mechanism of this vulnerability relies on a specific configuration scenario that is both documented and supported by the plugin developers. When an automation is set up where the Receive Webhook trigger includes an Is the user ID field, it expects to receive a user identifier in the request payload. However, if the corresponding Update-User action has its User ID field left blank while simultaneously mapping the Password field to the webhook password tag, the system defaults to updating the account associated with the provided user ID from the trigger rather than enforcing strict ownership or permission constraints on who can initiate the change. This configuration effectively creates a backdoor where any external entity possessing knowledge of a valid WordPress username and access to the public webhook endpoint can send a crafted request containing that username and a new password value.

The operational impact of this vulnerability is severe, leading directly to full account takeover capabilities for attackers. Because the flaw permits unauthenticated users to reset passwords for any WordPress account, including those with administrative privileges, an attacker can gain complete control over the compromised site. This level of access allows for further exploitation such as installing malicious plugins, defacing the website, stealing sensitive data stored within the database, or using the server as a pivot point for attacks against other internal systems. The ability to target administrator accounts specifically exacerbates the risk, as it compromises not just user-level content but also site-wide settings and security configurations.

This vulnerability aligns with CWE-287 Improper Authentication and CWE-306 Missing Authentication for Critical Function within standard classification frameworks. From a tactical perspective, it corresponds to ATT&CK technique T1595 Active Scanning as attackers may probe webhook endpoints, followed by T1136 Create Account or T1078 Valid Accounts if the attacker establishes persistent access through the compromised credentials. The exploitation path demonstrates how misconfigured integrations can inadvertently expose critical administrative functions to public networks without adequate safeguards.

Mitigation strategies must focus on immediate remediation and future configuration hardening. Administrators running affected versions should upgrade AutomatorWP Pro to version 1.4.5 or later, where the authorization logic has been corrected to properly validate user permissions before executing sensitive actions like password resets. In cases where upgrading is not immediately feasible, administrators should review their automation configurations to ensure that Update-User actions are never paired with blank User ID fields when handling webhook triggers. Additionally, implementing network-level controls such as IP whitelisting for webhook endpoints can provide an additional layer of defense by restricting access to trusted sources only. Regular security audits and adherence to the principle of least privilege in plugin configuration settings will help prevent similar authorization bypasses in other integrations.

Responsible

Wordfence

Reservation

11/10/2026

Disclosure

11/14/2026

Moderation

accepted

CPE

ready

EPSS

0.00537

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!