CVE-2025-32477
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 Jordi Salord WP-Easy Menu wp-easy-menu allows Stored XSS.This issue affects WP-Easy Menu: from n/a through <= 0.41.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the WP-Easy Menu plugin (versions up to 0.41) allows authenticated administrators to be tricked into performing unintended actions that inject malicious scripts (Stored XSS). Attackers can craft malicious links or forms that, when triggered by a logged-in admin, store persistent malicious code within the menu configuration that executes for all users viewing those menu pages.
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.
-
Confirm WP-Easy Menu plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP-Easy Menu' or 'Easy Menu' in the list. Note the displayed version number.Affected if Plugin is installed and version is 0.41 or lower
-
Verify the exact installed versionAccess the plugin files via FTP or file manager, open the main plugin PHP file (usually wp-easy-menu.php or similar) and locate the version definition in the header comments or a version constant.Affected if Version returned is 0.41 or any version lower than 0.41
-
Identify menu configuration storage locationCheck the WordPress database for tables related to the plugin (often wp_easy_menu or similar naming) or inspect the plugin code to find where menu items and their labels/URLs are stored. Look for POST handlers that save menu configuration data.Affected if Plugin stores menu item labels, URLs, or other display attributes without sanitization or with missing CSRF token validation
-
Inspect admin form submissions for CSRF protectionExamine the plugin PHP files for functions handling menu save/update actions. Look for nonce verification (wp_verify_nonce) or CSRF token validation in form handlers that process menu configuration submissions.Affected if Menu save/update handlers lack nonce verification or token validation checks, allowing forged requests
-
Review stored menu data for suspicious contentQuery the database for any menu items stored by the plugin and examine the content. Look for encoded scripts, event handlers, or HTML tags in menu label or URL fields.Affected if Menu configuration contains unsanitized JavaScript code, HTML script tags, or event handler attributes that could execute when viewed
You are affected if the WP-Easy Menu plugin is installed with version 0.41 or lower AND your menu configuration handlers lack CSRF token validation, allowing authenticated admins to be tricked into storing malicious scripts.
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 anti-CSRF tokens and request validation in the plugin to ensure requests originate from legitimate admin sessions; alternatively, update to a patched version if available or remove the plugin until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32477 — 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-32477 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