Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included <= 7.6.1.1 - Authenticated (Subscriber+) PHP Object Injection to Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 7.7.0
- Affected Plugin
- Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
- Affected Version
<= 7.6.1.1- CVSS
- 7.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-82627
At a glance
CVE-2026-82627 is a high-severity Deserialization of Untrusted Data vulnerability in the Uncanny Automator WordPress plugin, affecting versions <= 7.6.1.1. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 7.7.0; sites on affected versions should update now. Disclosed October 2026, reported by 0xd4rk5id3.
Vulnerability Overview
The Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.6.1.1 via deserialization of untrusted input. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object when a third-party integration plugin (such as PeepSo, MailPoet, WPForms, etc) is installed and a recipe is configured that stores attacker-controlled data as trigger meta. The additional presence of a POP chain within Uncanny Automator allows attackers to delete arbitrary files on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in Uncanny Automator <= 7.6.1.1 takes an account at Subscriber level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Uncanny Automator the fix is 7.7.0: builds <= 7.6.1.1 are affected, anything from 7.7.0 onward is not.
Remediation
Update to version 7.7.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Uncanny Automator 7.7.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
- 8.8CVE-2025-2075: Uncanny Automator Authenticated (Subscriber+)
CVE-2025-2075 - 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 - 5.5CVE-2024-13838: Uncanny Automator SSRF
CVE-2024-13838 - 5.4CVE-2025-4520: Uncanny Automator Authenticated (Subscriber+) Plugin
CVE-2025-4520 - 5.4Uncanny Automator <= 4.14 Cross-Site Request Forgery
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C