Security Resilience

CVE-2025-3623

RCE in Uncannyowl Uncanny Automator ≤ 6.4.0.2

Published
14 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.0087 58th percentile
Risk Priority 69 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-3623 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Uncannyowl Uncanny Automator. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Uncanny Automator plugin for WordPress is vulnerable to PHP Object Injection in all versions through 6.4.0.1. The flaw stems from unsafe deserialization of untrusted input inside the automator_api_decode_message() function in class-automator-recipe-helpers.php, which permits an attacker to supply a serialized PHP object. When a POP chain is present, the injected object can be leveraged to delete arbitrary files on the server.

Unauthenticated remote attackers can exploit the issue directly over the network without any user interaction or authentication. Successful exploitation results in high-impact outcomes limited to integrity and availability, specifically the ability to remove arbitrary files, while no confidentiality impact is indicated by the CVSS vector.

The vendor released version 6.4.0.2 on 2025-04-18 to address the vulnerability, with the corresponding patch committed to the WordPress plugin repository that updates the deserialization logic in the affected helper class. Public references, including the plugin changelog and Wordfence advisory, point to this update as the corrective measure.

The associated EPSS score has remained flat at 0.0109 with no material increase from its initial value.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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.…

more

The additional presence of a POP chain allows attackers to delete arbitrary files.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-13838Same product: Uncannyowl Uncanny Automator
CVE-2024-37118Same product: Uncannyowl Uncanny Automator
CVE-2024-37117Same product: Uncannyowl Uncanny Automator
CVE-2025-48133Same product: Uncannyowl Uncanny Automator
CVE-2025-2075Same product: Uncannyowl Uncanny Automator
CVE-2024-37119Same product: Uncannyowl Uncanny Automator
CVE-2025-4520Same product: Uncannyowl Uncanny Automator
CVE-2023-52151Same product: Uncannyowl Uncanny Automator
CVE-2026-77484Shared CWE-502
CVE-2025-66631Shared CWE-502

Affected Assets

uncannyowl
uncanny automator
≤ 6.4.0.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

References