WordPress security changelog
CRITICAL CVE-2025-3623 Analyzed

Uncanny Automator: Code execution

Uncanny Automator is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 9.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Uncanny Automator
Plugin slug
uncanny-automator
Affected
See vendor advisory
Safe version
See mitigation notes
Published
May 14, 2025
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published May 14, 2025 and is one of 12 known issues for this plugin.

What to do

Patch or disable the affected component.

Update Uncanny Automator to a release outside the affected range, or disable and remove it until a fixed version is available.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

References

Primary and upstream sources