Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-3623: The Uncanny Automator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and in

52
This month
CRITICAL 9.1REMOTEUPGRADE

CVE-2025-3623 is a critical-severity flaw (CVSS 9.1) affecting uncanny automator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.9% (top 41%)
CISA exploited listNo
WeaknessCWE-502
Published2025-05-14
Last modified2026-06-17
Publisher (CNA): Wordfence · Vendor: uncannyowl

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

uncannyowl uncanny automator UPGRADE
Affected: < 6.4.0.2
Fixed in: 6.4.0.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy uncanny-automator || rpm -q uncanny-automator || uncanny-automator --version
2. UPGRADE to 6.4.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade uncanny-automator
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade uncanny-automator
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-3623?

uncanny automator: upgrade to 6.4.0.2. Exact commands for each OS are on this page.

Is CVE-2025-3623 being exploited?

CVE-2025-3623 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-3623 affect?

CVE-2025-3623 affects uncanny automator. Severity is critical (CVSS 9.1). 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

How urgent is CVE-2025-3623?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.