# CVE-2026-25470: Code injection in ACPT (Pro) - Custom Post Types Plugin for WordPress

> Unauthenticated attackers can execute arbitrary code on WordPress sites using the ACPT Pro plugin, requiring an immediate upgrade.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-3xc6-wgx8-2ffv

## What is CVE-2026-25470?

CVE-2026-25470 is a critical code injection vulnerability in ACPT (Pro) - Custom Post Types Plugin for WordPress, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Remote Code Execution (RCE) in ACPT (Pro) - Custom Post Types Plugin for WordPress <= 2.0.47 versions.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-25470?


## How do I fix CVE-2026-25470?

No fix has been published for CVE-2026-25470 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25470 being exploited?

There is no known exploitation of CVE-2026-25470 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25470 and fix it if it is affected.

What it is: CVE-2026-25470 is a critical code injection vulnerability in ACPT (Pro) - Custom Post Types Plugin for WordPress, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25470 in the wild and no public exploit code.

Affected product: ACPT (Pro) - Custom Post Types Plugin for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25470/ (Markdown: https://insights.sbomify.com/CVE-2026-25470/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25470
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25470
- OSV: https://osv.dev/vulnerability/CVE-2026-25470

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25470/
Summaries are generated and may contain mistakes; the official description above is the record.