ZeroBreach Request early access
← All Attack Surface
high CVE-2026-82627

PHP object injection in Uncanny Automator lets subscriber accounts delete files (CVE-2026-82627)

Tags: wordpress, php, plugin, uncanny-automator, object-injection

The Uncanny Automator plugin for WordPress, versions through 7.6.1.1, is vulnerable to PHP object injection through deserialization of untrusted input (CVE-2026-82627, CVSS 7.5, published October 8, 2026). An attacker with Subscriber-level access can inject a PHP object when a third-party integration (such as PeepSo, MailPoet, or WPForms) is installed and a recipe is configured to store attacker-controlled data as trigger meta. A property-oriented programming chain inside the plugin turns that object injection into arbitrary file deletion on the server.

Sites most at risk run automation recipes alongside integrations that accept user-submitted content, such as community, mailing list, and form-driven sites. Exploitation needs a low-privilege account plus that specific recipe configuration, so the impact is real but conditional. No exploitation in the wild has been reported yet, and the vendor has committed a fix on WordPress.org.

What to do

  • Update Uncanny Automator to 7.7.0 or a newer patched version (the vendor lists 7.7.0 as the patched release).
  • If you cannot update immediately, temporarily disable the plugin or the affected recipes, and limit new Subscriber registrations.
  • Review recipe configurations for trigger meta fed by user-controlled fields, and check logs and the filesystem for missing or altered files.

A forgotten automation plugin with a known flaw is exactly what recurring scans are built to catch. ZeroBreach inventories every plugin on the server and flags vulnerable versions on schedule, and edge WAF rules buy you time while you patch.