Uncanny Automator < 6.10.0 - Authenticated (Subscriber+) Information Exposure
Strategic Overview
- Status
- Patched in 6.10.0
- Affected Plugin
- Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
- Affected Version
< 6.10.0- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-66056
At a glance
CVE-2025-66056 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Uncanny Automator WordPress plugin, affecting versions < 6.10.0. 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 6.10.0; sites on affected versions should update now. Disclosed November 2025, reported by Legion Hunter.
Vulnerability Overview
The Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 6.10.0 (exclusive). This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Uncanny Automator < 6.10.0 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Uncanny Automator the fix is 6.10.0: builds < 6.10.0 are affected, anything from 6.10.0 onward is not.
Remediation
Update to version 6.10.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Uncanny Automator 6.10.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
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.8CVE-2025-2075: Uncanny Automator Authenticated (Subscriber+)
CVE-2025-2075 - 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.5CVE-2026-15025: Uncanny Automator Authenticated (Subscriber+)
CVE-2026-15025 - 7.2CVE-2026-2269: Uncanny Automator SSRF to Arbitrary File Upload
CVE-2026-2269 - 6.5CVE-2025-48133: Uncanny Automator Missing Authorization
CVE-2025-48133 - 6.4CVE-2025-15522: Uncanny Automator Stored XSS
CVE-2025-15522
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C