Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-56031 – Unauthenticated PHP Object Injection – Uncanny Automator WordPress Plugin ≤ 7.3.1.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-56031 is a high-severity, unauthenticated PHP Object Injection vulnerability affecting the Uncanny Automator WordPress plugin (by Uncanny Owl) in all versions up to and including 7.3.1.2. The flaw arises from insufficient protection against deserialization of untrusted data when processing user-submitted trigger token values, and carries a CVSS v3.1 base score of 8.1 (HIGH). Successful exploitation — where a suitable Property-Oriented Programming (POP) chain exists in the target environment — can result in remote code execution, arbitrary file manipulation, or full site compromise.

Technical details

  • Root cause: The plugin fails to adequately sanitize or validate user-submitted trigger token values before passing them to PHP’s deserialization routines (CWE-502: Deserialization of Untrusted Data). Specific integrations affected include the plugin’s handling of trigger token data in WPForms, MailPoet, and FunnelKit (Autonami) workflows.
  • Trigger conditions: An unauthenticated attacker can deliver a crafted, serialized PHP object payload through an affected trigger token input. No account, session, or victim interaction is required.
  • Attack vector: Remotely exploitable over the network (AV:N) with no privileges required (PR:N) and no user interaction (UI:N). Attack complexity is rated High (AC:H), reflecting that exploitation depends on the presence of a usable POP chain within the target WordPress environment’s installed codebase.
  • Impact: If a valid POP chain is available, exploitation can yield remote code execution (RCE), arbitrary file read/write/deletion, sensitive data exfiltration, or complete site takeover. CVSS impact subscores are High across Confidentiality, Integrity, and Availability (C:H/I:H/A:H).

Affected software

  • Uncanny Automator (free/lite) — all versions ≤ 7.3.1.2
  • Uncanny Automator Pro — all versions ≤ 7.3.1.2

Severity

  • CVSS v3.1 Base Score: 8.1 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action — update the plugin: Upgrade Uncanny Automator (free and Pro) to version 7.3.1.3 or later, which contains Uncanny Owl’s fix for this vulnerability. Updates are available through the official WordPress plugin updater in your dashboard or through the WordPress.org plugin repository. Do not install plugin builds from unofficial sources.
  • Audit your WordPress environment: Assess which other plugins are installed alongside Uncanny Automator, as the availability of a POP chain is determined by the broader plugin/theme codebase present on each site. Even in the absence of a known public exploit, environments with complex plugin sets carry elevated risk.
  • Network mitigation (if immediate patching is not feasible): Restrict public access to WordPress endpoints that process trigger token data, or place the WordPress installation behind a Web Application Firewall (WAF) configured to detect and block PHP deserialization payloads.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge