CVE-2025-32484
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Mathieu Chartier WP-Planification wp-planification allows Stored XSS.This issue affects WP-Planification: from n/a through <= 2.3.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP-Planification WordPress plugin (versions up to 2.3.1) allows authenticated administrators to unknowingly inject malicious scripts through stored XSS. Attackers can craft malicious requests that, when triggered by a logged-in administrator, cause the XSS payload to be stored in the database and executed when other users view the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the WP-Planification plugin filesNavigate to /wp-content/plugins/ in your WordPress installation and check if a folder named 'wp-planification' or similar existsAffected if The plugin folder is present in the plugins directory
-
Identify the installed plugin versionOpen the main plugin PHP file (usually wp-planification.php) and look for a version comment or header that specifies the current version numberAffected if The version number is 2.3.1 or lower (or if no version is found but the plugin is present, assume affected)
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and check whether WP-Planification is activatedAffected if The plugin shows as active in the WordPress admin panel
-
Inspect stored plugin data for XSS payloadsCheck the WordPress database tables where plugin data is stored (often wp_options or custom tables) for any suspicious script tags, html tags, or encoded JavaScript that could indicate XSS exploitationAffected if Stored data contains unexpected script tags, event handlers (onerror, onload, onclick), or other XSS vectors in plugin-related entries
Your environment is affected if the WP-Planification plugin is installed, active, and running version 2.3.1 or lower, or if suspicious XSS payloads are found in plugin-stored data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin data; validate the nonce before processing any state-changing request. Until patched, restrict administrative access and monitor for suspicious admin activity.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data