Uncanny Automator <= 6.4.0.2 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update
Strategic Overview
- Status
- Patched in 6.5.0
- Affected Plugin
- Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
- Affected Version
<= 6.4.0.2- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-4520
At a glance
CVE-2025-4520 is a medium-severity Missing Authorization vulnerability in the Uncanny Automator WordPress plugin, affecting versions <= 6.4.0.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.5.0; sites on affected versions should update now. Disclosed May 2025, reported by mikemyers.
Vulnerability Overview
The Uncanny Automator plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on multiple AJAX functions in versions up to, and including, 6.4.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions or above to update plugin settings.
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 Uncanny Automator <= 6.4.0.2 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 Uncanny Automator the fix is 6.5.0: builds <= 6.4.0.2 are affected, anything from 6.5.0 onward is not.
Remediation
Update to version 6.5.0, 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: Uncanny Automator 6.5.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2025-2075: Uncanny Automator Authenticated (Subscriber+)
CVE-2025-2075 - 7.5CVE-2026-15025: Uncanny Automator Authenticated (Subscriber+)
CVE-2026-15025 - 6.5CVE-2025-48133: Uncanny Automator Missing Authorization
CVE-2025-48133 - 4.3CVE-2025-58193: Uncanny Automator <= 6.7.0.1 Missing Authorization
CVE-2025-58193
Other vulnerabilities in Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
- 9.1CVE-2025-3623: Uncanny Automator PHP Object Injection
CVE-2025-3623 - 8.1CVE-2026-15008: Uncanny Automator PHP Object Injection
CVE-2026-15008 - 8.1CVE-2026-56031: Uncanny Automator PHP Object Injection
CVE-2026-56031 - 7.2CVE-2026-2269: Uncanny Automator SSRF to Arbitrary File Upload
CVE-2026-2269 - 6.4CVE-2025-15522: Uncanny Automator Stored XSS
CVE-2025-15522 - 5.5CVE-2024-13838: Uncanny Automator SSRF
CVE-2024-13838 - 5.4Uncanny Automator <= 4.14 Cross-Site Request Forgery
- 5.3CVE-2023-52151: Uncanny Automator <= 5.1.0.2 Info Exposure
CVE-2023-52151
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C