dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-32661

HIGH · 7.1 CVSS v3.1 Published 2025-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in WP Map Plugins Interactive US Map interactive-us-map allows Stored XSS.This issue affects Interactive US Map: from n/a through <= 2.7.

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 confidence

A CSRF vulnerability in the Interactive US Map WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions that result in Stored XSS. The lack of anti-CSRF token validation on state-changing operations enables malicious requests to be executed, and insufficient input sanitization causes the XSS payload to be stored and executed when other users view the map.

MitigationImplement anti-CSRF nonce verification on all plugin state-changing operations and apply proper input sanitization with context-aware output encoding to prevent Stored XSS. Consider updating to a patched version if available.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Interactive US Map plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Interactive US Map' is installed and active. Note the installed version number displayed in the plugin list.
    Affected if The plugin is installed and active with no patched version applied.
  2. Locate and inspect plugin state-changing handlers
    Access the plugin files via FTP or file manager at wp-content/plugins/interactive-us-map/. Examine PHP files that handle form submissions, particularly files processing admin settings, map data, or configuration updates.
    Affected if State-changing operations (save, update, import) are found without nonce verification code.
  3. Check for anti-CSRF token validation
    Search plugin PHP files for 'wp_nonce_field', 'wp_verify_nonce', 'check_admin_referer', or similar nonce verification functions within all form handlers and AJAX endpoints. Use grep or manual code review.
    Affected if No nonce verification is present in functions that modify plugin settings, map data, or state.
  4. Inspect input sanitization on map data fields
    Review PHP files that process user-supplied data (map labels, descriptions, tooltips, settings inputs). Look for sanitization functions like esc_html, esc_attr, sanitize_text_field, or output encoding before storing or displaying data.
    Affected if User input is stored or displayed without proper sanitization, allowing HTML/JavaScript injection.
  5. Test for Stored XSS via plugin admin interface
    Using an admin account, access the plugin settings. Input a test XSS payload (e.g., <script>alert('XSS')</script>) into map label, tooltip, or description fields, save, then view the map frontend to confirm execution.
    Affected if The XSS payload executes when viewing the map, confirming the vulnerability is present and exploitable.

A user is affected if the Interactive US Map plugin is installed with unpatched code lacking anti-CSRF nonces and proper input sanitization, allowing Stored XSS via admin-triggered requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF nonce verification on all plugin state-changing operations and apply proper input sanitization with context-aware output encoding to prevent Stored XSS. Consider updating to a patched version if available.

Recommended fix Moderate confidence

Latest version of Interactive US Map plugin (version greater than 2.7)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Interactive US Map' plugin (by WP Map Plugins)
  4. 4. Check the current installed version is 2.7 or below
  5. 5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress.org plugin repository
  6. 6. Verify the update completes successfully
  7. 7. Test the map functionality to ensure it works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32661 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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