# CVE-2026-32564: WordPress ACPT (Pro) - Custom Post Types Plugin for WordPress plugin <= 2.0.63 - SQL Injection vulnerability

> Subscribers can exploit SQL injection in the ACPT Pro plugin to read or modify database contents.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-9hrm-9f56-944v

## What is CVE-2026-32564?

CVE-2026-32564 is a high-severity SQL injection vulnerability in ACPT (Pro) - Custom Post Types Plugin for WordPress, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber SQL Injection in ACPT (Pro) - Custom Post Types Plugin for WordPress <= 2.0.63 versions.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-32564 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32564 is a high-severity SQL injection vulnerability in ACPT (Pro) - Custom Post Types Plugin for WordPress, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32564 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-32564/ (Markdown: https://insights.sbomify.com/CVE-2026-32564/index.md)
```

## Sources

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

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