dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-25470

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in ACPT ACPT (Pro) - Custom Post Types Plugin for WordPress allows Remote Code Inclusion. This issue affects ACPT (Pro) - Custom Post Types Plugin for WordPress: from n/a through 2.0.47.

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 · moderate confidence

Code Injection vulnerability in ACPT (Pro) WordPress plugin allows remote attackers to include and execute arbitrary code through improper control of code generation. The CVSS 10 score indicates trivial network exploitation without authentication, leading to complete system compromise.

MitigationUpdate ACPT plugin to latest version once available; disable plugin if no patch exists; implement WAF rules to block suspicious include/require requests; review server for indicators of compromise.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ACPT Pro plugin installation
    Navigate to WordPress admin dashboard > Plugins and verify ACPT (Pro) is listed as an active or installed plugin
    Affected if ACPT (Pro) plugin is installed and active on the WordPress site
  2. Identify installed ACPT Pro version
    In WordPress admin, go to Plugins > Installed Plugins > click on ACPT Pro details to view the version number
    Affected if The installed version has not been patched and matches vulnerable release(s)
  3. Inspect for unauthorized PHP files
    Check the wp-content/uploads/ directory and plugin directories for unknown .php files with suspicious names (e.g., shell.php, backdoor.php, or base64-encoded scripts)
    Affected if Unexpected PHP files exist in upload directories or plugin folders that were not deliberately placed by administrators
  4. Review access logs for code injection patterns
    Examine web server access logs (Apache/nginx) for suspicious requests containing include, require, eval, or base64 strings in URL parameters, particularly targeting ACPT-related endpoints
    Affected if Logs show repeated requests with malicious include/require patterns or PHP code execution attempts via ACPT endpoints
  5. Check for unauthorized admin accounts
    In WordPress admin, go to Users and review the list for unfamiliar administrator accounts or user role modifications
    Affected if Unknown administrator accounts exist that were not created by legitimate site administrators

A user is affected if ACPT (Pro) plugin is installed, the version is unpatched, and indicators show unauthorized code execution or attacker presence on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ACPT plugin to latest version once available; disable plugin if no patch exists; implement WAF rules to block suspicious include/require requests; review server for indicators of compromise.

Recommended fix Moderate confidence

Latest version after 2.0.47 (check WordPress plugin repository for current release)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate ACPT (Pro) - Custom Post Types Plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository or the vendor's website
  6. 6. After updating, verify the plugin is functioning correctly and test critical functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25470 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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