AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI < 6.0.8 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 6.0.8
- Affected Plugin
- AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI
- Affected Version
< 6.0.8- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery
- CVE
CVE-2026-121472
At a glance
CVE-2026-121472 is a medium-severity Cross-Site Request Forgery vulnerability in the AutomatorWP WordPress plugin, affecting versions < 6.0.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.8; sites on affected versions should update now. Disclosed November 2026, reported by kta1kri.
Vulnerability Overview
The AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 6.0.8. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery
Reaching this weakness in AutomatorWP < 6.0.8 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For AutomatorWP the fix is 6.0.8: builds < 6.0.8 are affected, anything from 6.0.8 onward is not.
Remediation
Update to version 6.0.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to AutomatorWP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AutomatorWP 6.0.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI
- 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.5CVE-2026-104768: AutomatorWP Privilege Escalation
CVE-2026-104768 - 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 - 5.4CVE-2025-9542: AutomatorWP <= 5.3.7 Multiple Functions
CVE-2025-9542
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C