CVE-2026-12375

Uncanny Automator Pro 7.3.0.5 - Maliciously Injected Backdoor

2026-06-16 00:00

Strategic Overview

Status: Patched in 7.3.0.6
Affected Plugin: Uncanny Automator Pro
Affected Version: 7.3.0.5
CVSS: 9.8Critical
Weakness type: CWE-506 · Embedded Malicious Code
CVE: CVE-2026-12375

View all Uncanny Automator Pro vulnerabilities

At a glance

CVE-2026-12375 is a critical-severity Embedded Malicious Code vulnerability in the Uncanny Automator Pro WordPress plugin, affecting versions 7.3.0.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 7.3.0.6; sites on affected versions should update now. Disclosed June 2026, reported by Mike Gozdiskowski.

Vulnerability Overview

The Uncanny Automator Pro plugin for WordPress contains a backdoor in all versions up to, and including, 7.3.0.5. This is due to plugin's distribution server getting compromised. This made it possible for attackers to access compromised instances.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-506: Embedded Malicious Code

Reaching this weakness in Uncanny Automator Pro 7.3.0.5 takes a caller who can reach the endpoint. Embedded malicious code means functionality was deliberately placed in the software to act against the site owner's interest, rather than being an accidental defect.

Removing the software is not enough on its own — anything it created or modified while active has to be audited too. For Uncanny Automator Pro the fix is 7.3.0.6: builds 7.3.0.5 are affected, anything from 7.3.0.6 onward is not.

Remediation

Update to version 7.3.0.6, or a newer patched version

How does WordSec protect against this?

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 Pro 7.3.0.6 closes this, and updating the plugin is the step that ends it.

Scanner
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-12375 https://www.wordfence.com/threat-intel/vulnerabilities/id/8571b80b-a76d-4ade-98c9-c0bd44eee344 https://nvd.nist.gov/vuln/detail/CVE-2026-12375

Related records

Other vulnerabilities in Uncanny Automator Pro

CVSS Vector

9.8

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/