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

CVE-2025-23665

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Ravi Kumar Vanukuru RSV GMaps rsv-google-maps allows Stored XSS.This issue affects RSV GMaps: from n/a through <= 1.5.

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

CSRF vulnerability in the RSV GMaps WordPress plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject stored XSS payloads into map data. Since the XSS is stored, it executes for all users viewing the affected Google Maps content.

MitigationImplement anti-CSRF tokens (nonces) on all admin-side forms and AJAX actions, and ensure all user-supplied map data is properly sanitized before storage and escaped during output.

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 RSV GMaps plugin is installed
    Navigate to WordPress admin > Plugins and look for 'RSV GMaps' in the installed plugins list, or check the filesystem at wp-content/plugins/ for an rsv-gmaps or similar directory
    Affected if The RSV GMaps plugin is present in the WordPress installation
  2. Check plugin version
    In WordPress admin > Plugins > RSV GMaps, view the plugin details to find the installed version number, or read the main plugin PHP file header for the Version field
    Affected if The installed version is any version prior to the patched release (compare against official WordPress repository for latest fixed version)
  3. Verify plugin is active
    Check WordPress admin > Plugins > Installed Plugins to see if RSV GMaps shows as 'Active'
    Affected if RSV GMaps is currently activated
  4. Inspect map data for XSS payloads
    Access the plugin settings or map configuration pages in the WordPress admin (typically under Settings or a dedicated RSV GMaps menu), and examine any stored map entries for suspicious script tags, javascript: URIs, or HTML event handlers such as onload, onerror, or onclick
    Affected if Any map data entry contains unescaped HTML, script tags, or JavaScript event handlers
  5. Review map output for unescaped content
    Visit a page on the site that displays a Google Map embed from the plugin, view the page source, and check if map location names, addresses, or descriptions contain raw HTML that should be escaped
    Affected if Displayed map content contains visible HTML tags or executes JavaScript when the map is viewed

A defender is affected if the RSV GMaps WordPress plugin is installed and active, with any version that lacks CSRF protection on admin forms storing unsanitized map data that could contain XSS payloads.

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

Implement anti-CSRF tokens (nonces) on all admin-side forms and AJAX actions, and ensure all user-supplied map data is properly sanitized before storage and escaped during output.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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