# CVE-2025-32583: WordPress PDF 2 Post Plugin <= 2.4.0 - Remote Code Execution (RCE) vulnerability

> Attackers can execute arbitrary code remotely via improper code generation in the PDF 2 Post WordPress plugin.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 17 Apr 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-23w5-m3rw-wr6g

## What is CVE-2025-32583?

CVE-2025-32583 is a critical code injection vulnerability in termel PDF 2 Post, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in termel PDF 2 Post pdf2post allows Remote Code Inclusion.This issue affects PDF 2 Post: from n/a through <= 2.4.0.

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

## Which versions are affected by CVE-2025-32583?


## How do I fix CVE-2025-32583?

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

## Is CVE-2025-32583 being exploited?

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

Public exploit code:

-  WordPress PDF 2 Post Plugin <= 2.4.0 is vulnerable to Remote Code Execution (RCE) +Subscriber (github_poc): https://github.com/Nxploited/CVE-2025-32583

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32583 and fix it if it is affected.

What it is: CVE-2025-32583 is a critical code injection vulnerability in termel PDF 2 Post, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32583 in the wild and no public exploit code.

Affected product: termel PDF 2 Post. 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-2025-32583/ (Markdown: https://insights.sbomify.com/CVE-2025-32583/index.md)
```

## Sources

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

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