CVE-2025-2247: The WP-PManager WordPress plugin through 1.2 does not have CSRF check in place when updating its settings, whi

Q: How do I fix CVE-2025-2247?

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

Q: Is CVE-2025-2247 being exploited?

CVE-2025-2247 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-2025-2247 affect?

CVE-2025-2247 affects wp-pmanager. Severity is medium (CVSS 5.4). The WP-PManager WordPress plugin through 1.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

Q: How urgent is CVE-2025-2247?

Priority 25/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2025-2247 is a medium-severity flaw (CVSS 5.4) 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 have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 94%)
CISA exploited list	No
Weakness	CWE-352
Published	2025-05-15
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-05-15 20:16 UTCPublished CVE record published
2026-06-17 09:06 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-2025-2247?

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

Is CVE-2025-2247 being exploited?

CVE-2025-2247 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-2025-2247 affect?

CVE-2025-2247 affects wp-pmanager. Severity is medium (CVSS 5.4). The WP-PManager WordPress plugin through 1.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

How urgent is CVE-2025-2247?

Priority 25/100. 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-2024-13875 HIGH 7.1 UPGRADE The WP-PManager WordPress plugin through 1.2 does not sanitise and escape a parameter before outputting it bac

References

← Back to latest CVEs