CVE-2025-3623

Uncanny Automator <= 6.4.0.1 - Unauthenticated PHP Object Injection in automator_api_decode_message Function

2025-05-13 14:20
mikemyers

Strategic Overview

Status
Patched in 6.4.0.2
Affected Plugin
Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
Affected Version
<= 6.4.0.1
CVSS
9.1Critical
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2025-3623
View all Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included vulnerabilities

At a glance

CVE-2025-3623 is a critical-severity Deserialization of Untrusted Data vulnerability in the Uncanny Automator WordPress plugin, affecting versions <= 6.4.0.1. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.4.0.2; sites on affected versions should update now. Disclosed May 2025, reported by mikemyers.

Vulnerability Overview

The Uncanny Automator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.4.0.1 via deserialization of untrusted input in the automator_api_decode_message() function. This makes it possible for unauthenticated to inject a PHP Object. The additional presence of a POP chain allows attackers to delete arbitrary files.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-502: Deserialization of Untrusted Data

Uncanny Automator <= 6.4.0.1 carries this weakness at automator_api_decode_message(), and reaching it takes no account at all. 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 6.4.0.2: builds <= 6.4.0.1 are affected, anything from 6.4.0.2 onward is not.

Remediation

Update to version 6.4.0.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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 6.4.0.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2025-3623https://www.wordfence.com/threat-intel/vulnerabilities/id/00bcfd8f-9785-449a-a0ea-16e2583d684ahttps://nvd.nist.gov/vuln/detail/CVE-2025-3623

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C