CVE-2025-32621
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 Vsourz Digital WP Map Route Planner wp-map-route-planner allows Cross Site Request Forgery.This issue affects WP Map Route Planner: from n/a through <= 1.0.0.
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 Map Route Planner WordPress plugin. Attackers can trick authenticated administrators into submitting unintended requests by crafting malicious links or pages, potentially leading to unauthorized configuration changes or data manipulation.
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 Map Route Planner plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Map Route Planner' or check the wp-content/plugins directory for a folder containing 'wp-map-route-planner'Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Map Route Planner, and note the version number displayed below the plugin nameAffected if Version cannot be determined or is unknown, proceed to code inspection
-
Inspect plugin admin forms for nonce verificationAccess the plugin source code in wp-content/plugins and examine PHP files in admin/pages for form submissions. Search for 'wp_nonce_field' or 'check_admin_referer' functions in all <form> tagsAffected if Forms exist without wp_nonce_field() or check_admin_referer() calls
-
Inspect AJAX actions for nonce verificationSearch plugin PHP files for 'add_action' hooks containing 'wp_ajax'. For each AJAX handler, verify the presence of 'check_ajax_referer' or 'wp_verify_nonce' at the handler function entry pointAffected if AJAX actions handle requests without nonce verification
-
Check plugin settings pages for unprotected configurationNavigate to all WP Map Route Planner admin menu items (usually under Settings or a dedicated menu), locate any forms that modify plugin settings, routes, or map configurations, and verify each form includes a nonce fieldAffected if Configuration forms exist without CSRF protection tokens
If the WP Map Route Planner plugin is installed and any of its admin forms or AJAX handlers lack WordPress nonce verification, the installation is vulnerable to CVE-2025-32621.
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 form submissions and AJAX actions within the plugin to verify the request origin and intent.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32621 — 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-32621 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