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

CVE-2025-32617

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 Ydesignservices Multiple Location Google Map multiple-location-google-map allows Stored XSS.This issue affects Multiple Location Google Map: from n/a through <= 1.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 confidence

Cross-Site Request Forgery vulnerability in the Ydesignservices Multiple Location Google Map WordPress plugin allows authenticated attackers to inject malicious scripts via Stored XSS. Attackers can exploit this by tricking an administrator into performing an unintended action (e.g., visiting a malicious URL), resulting in script execution within the admin context.

MitigationUpdate to a patched version when available; implement anti-CSRF tokens for all state-changing operations and apply proper input validation/sanitization to prevent XSS.

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. Identify if the Ydesignservices Multiple Location Google Map plugin is installed
    Navigate to WordPress admin > Plugins and search for 'Ydesignservices Multiple Location Google Map' or check the /wp-content/plugins/ directory for a folder containing 'ydesignservices' or similar naming
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its details; or inspect the plugin's main PHP file for a 'Version' header comment
    Affected if The version number matches or falls within any known vulnerable version range (if such information becomes available)
  3. Inspect stored map location data for unsanitized content
    Access the WordPress database (via phpMyAdmin or CLI) and query the wp_options table or custom plugin tables for map location entries; look for any location names, addresses, or coordinates that contain HTML/script tags
    Affected if Location data contains unescaped HTML or JavaScript code such as <script> tags or event handlers like onerror=, onload=
  4. Verify if CSRF protection is implemented on plugin admin actions
    Examine the plugin's PHP source code for presence of wp_nonce_field() or check_admin_referer() calls when saving map location settings; inspect forms that submit location data for nonce fields
    Affected if Forms saving location data lack nonce verification tokens or the tokens are not validated on submission
  5. Test for Stored XSS by examining admin dashboard rendering
    If you have access to a test environment, add a map location with a name containing a simple XSS payload like <img src=x onerror=alert(1)>; then view the map in the admin panel to see if the script executes
    Affected if The XSS payload executes (triggers an alert or visible script behavior) when viewing the map location in the admin interface

A user is affected if the Ydesignservices Multiple Location Google Map plugin is installed and either lacks CSRF token protection on its location save functions or contains unsanitized stored location data that executes JavaScript in the admin context.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; implement anti-CSRF tokens for all state-changing operations and apply proper input validation/sanitization to prevent XSS.

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32617 — 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-32617 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