CVE-2024-13875: The WP-PManager WordPress plugin through 1.2 does not sanitise and escape a parameter before outputting it bac

Q: How do I fix CVE-2024-13875?

wp-pmanager: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-13875 being exploited?

CVE-2024-13875 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13875 affect?

CVE-2024-13875 affects wp-pmanager. Severity is high (CVSS 7.1). 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.

Q: How urgent is CVE-2024-13875?

Priority 35/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2024-13875 is a high-severity flaw (CVSS 7.1) affecting wp-pmanager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-03-20
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: mantus667

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-20 06:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

mantus667 wp-pmanager UPGRADE

Affected: <= 1.2

Fixed in: newer than 1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-pmanager || rpm -q wp-pmanager || wp-pmanager --version

2. UPGRADE to newer than 1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-pmanager

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-pmanager

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13875?

wp-pmanager: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Is CVE-2024-13875 being exploited?

CVE-2024-13875 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13875 affect?

CVE-2024-13875 affects wp-pmanager. Severity is high (CVSS 7.1). 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.

How urgent is CVE-2024-13875?

Priority 35/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-2248 MEDIUM 5.4 UPGRADE The WP-PManager WordPress plugin through 1.2 does not sanitize and escape a parameter before using it in a SQL
CVE-2025-2247 MEDIUM 5.4 UPGRADE The WP-PManager WordPress plugin through 1.2 does not have CSRF check in place when updating its settings, whi

References

← Back to latest CVEs