# CVE-2024-13875: WP Programmmanager <= 1.2 - Reflected XSS

> Reflected XSS in WP-PManager allows attackers to execute scripts against admin users, potentially leading to account takeover.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-pph8-wh6p-w5m7

## What is CVE-2024-13875?

CVE-2024-13875 is a high-severity cross-site scripting vulnerability in Unknown WP-PManager, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP-PManager WordPress plugin through 1.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-13875?

It affects 1 product.


Products: Mantus667 Wp-Pmanager.

## How do I fix CVE-2024-13875?

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

## Is CVE-2024-13875 being exploited?

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

## Other vulnerabilities in Unknown WP-PManager

- [CVE-2025-2247](https://insights.sbomify.com/CVE-2025-2247/): WP-PManager <= 1.2 - Category Deletion via CSRF (medium 5.4)
- [CVE-2025-2248](https://insights.sbomify.com/CVE-2025-2248/): WP-PManager <= 1.2 - Admin+ SQL Injection (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13875 and fix it if it is affected.

What it is: CVE-2024-13875 is a high-severity cross-site scripting vulnerability in Unknown WP-PManager, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-13875 in the wild and no public exploit code.

Affected product: Unknown WP-PManager. 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-2024-13875/ (Markdown: https://insights.sbomify.com/CVE-2024-13875/index.md)
```

## Sources

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

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