AutomatorWP <= 5.8.4 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via automatorwp_convertkit_get_forms AJAX Action
Strategic Overview
- Status
- Patched in 5.8.5
- Affected Plugin
- AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress
- Affected Version
<= 5.8.4- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-76057
At a glance
CVE-2026-76057 is a medium-severity Missing Authorization vulnerability in the AutomatorWP WordPress plugin, affecting versions <= 5.8.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.8.5; sites on affected versions should update now. Disclosed August 2026, reported by Wordfence PRISM.
Vulnerability Overview
The AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.8.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve all ConvertKit form data configured by the site's manager account, exposing integration details intended to be restricted to plugin managers. The required nonce is localized on every admin page load, making it accessible to any authenticated user who can reach /wp-admin.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in AutomatorWP <= 5.8.4 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AutomatorWP the fix is 5.8.5: builds <= 5.8.4 are affected, anything from 5.8.5 onward is not.
Remediation
Update to version 5.8.5, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AutomatorWP 5.8.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress
- 9.6CVE-2024-12626: AutomatorWP <= 5.0.9 Reflected Cross-Site Scripting
CVE-2024-12626 - 8.8CVE-2021-24717: AutomatorWP <= 1.7.5 Privilege Escalation
CVE-2021-24717 - 8.0CVE-2025-9539: AutomatorWP Authenticated (Subscriber+) RCE
CVE-2025-9539 - 7.2CVE-2026-42775: AutomatorWP Stored XSS
CVE-2026-42775 - 7.2CVE-2026-42650: AutomatorWP Stored XSS
CVE-2026-42650 - 7.2CVE-2025-5487: AutomatorWP <= 5.2.5 SQL Injection
CVE-2025-5487 - 4.9CVE-2025-68561: AutomatorWP <= 5.2.4 SQL Injection
CVE-2025-68561 - 4.9CVE-2025-48280: AutomatorWP <= 5.2.1.3 SQL Injection
CVE-2025-48280
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C