CVE-2026-12375
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe uncanny-automator-pro WordPress plugin before 7.3.0.6 was distributed with malicious code after the vendor's uncanny-automator-pro WordPress plugin before 7.3.0.6 update/distribution infrastructure was compromised; the injected backdoor grants unauthenticated attackers an administrator session on affected sites and beacons the site's secret keys and administrator details to attacker-controlled servers.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe uncanny-automator-pro WordPress plugin versions before 7.3.0.6 contained malicious code injected via a compromise of the vendor's update/distribution infrastructure. The injected backdoor allows unauthenticated attackers to obtain administrator session credentials and exfiltrates site secret keys and administrator details to attacker-controlled servers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify installed plugin versionNavigate to WordPress admin > Plugins and locate 'Uncanny Automator Pro' in the installed plugins list. The version number is displayed beneath the plugin name.Affected if The displayed version number is lower than 7.3.0.6 (e.g., 7.3.0.5, 7.3.0, any version before 7.3.0.6).
-
Inspect WordPress user accounts for unauthorized administratorsGo to WordPress admin > Users and review the list of user accounts with the Administrator role. Look for unfamiliar accounts, accounts with unusual usernames, or accounts created without your knowledge.Affected if There are administrator accounts you did not create, or accounts with suspicious usernames that were added without authorization.
-
Check WordPress configuration for altered secret keysOpen the wp-config.php file in the WordPress root directory and review the AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, and NONCE_KEY values. Compare them to your known values or look for unexpected, long random-looking strings that differ from your original configuration.Affected if The secret keys and salts in wp-config.php have been changed or contain unfamiliar values different from what you originally set.
-
Review server access logs for suspicious outbound connectionsExamine your web server access logs (often in /var/log/apache2/, /var/log/nginx/, or your hosting provider's log viewer) for outgoing HTTP requests from your server to unfamiliar external IP addresses or domains, particularly those containing paths like /wp-json/ or unusual parameter patterns.Affected if Logs show outbound requests from your server to unknown external domains, especially requests sending what appears to be WordPress credential or configuration data.
-
Audit recently modified plugin filesIf possible, compare the current uncanny-automator-pro plugin files against a clean version from the vendor or a known good backup. Look for unexpected PHP files, base64-encoded code blocks, or files with recent modification dates that you did not authorize.Affected if The plugin directory contains unfamiliar PHP files, code that appears obfuscated or encoded, or files modified at times you did not make changes.
Your environment is affected if the installed Uncanny Automator Pro plugin version is below 7.3.0.6, or if you detect unauthorized administrator accounts, modified secret keys, suspicious outbound connections, or unexpected files in the plugin directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately update the plugin to version 7.3.0.6 or later, rotate all WordPress secret keys and salts, audit for unauthorized administrator accounts, and review server access logs for indicators of compromise.
uncanny-automator-pro version 7.3.0.6 or later
- Update uncanny-automator-pro plugin to version 7.3.0.6 or later through WordPress admin or via wp-cli command: wp plugin update uncanny-automator-pro
- After updating, review all user accounts for unauthorized administrator accounts and remove any suspicious entries
- Rotate WordPress authentication keys and salts in wp-config.php by regenerating them
- Audit server access logs for requests to attacker-controlled domains or unusual beaconing behavior
- Consider performing a full security audit of the WordPress installation since the compromise occurred through the vendor's distribution infrastructure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data