CVE-2026-82627 Deserialization in Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
Authenticated attackers can delete arbitrary files via PHP object injection if specific third-party integrations are configured.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-82627?
CVE-2026-82627 is a high-severity unsafe deserialization vulnerability in uncannyowl Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-502
Which versions are affected by CVE-2026-82627?
How do I fix CVE-2026-82627?
No fix has been published for CVE-2026-82627 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-82627 being exploited?
There is no known exploitation of CVE-2026-82627 in the wild and no public exploit code.
Sources
Also known as GHSA-fg33-378f-xr8h.