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

CVE-2025-48304

HIGH · 7.1 CVSS v3.1 Published 2025-08-28
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 Gary Illyes Google XML News Sitemap plugin gn-xml-sitemap allows Stored XSS.This issue affects Google XML News Sitemap plugin: from n/a through <= 0.02.

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 (CSRF) vulnerability in the Gary Illyes Google XML News Sitemap WordPress plugin (gn-xml-sitemap) allows authenticated or unauthenticated attackers to craft malicious requests that result in Stored Cross-Site Scripting (XSS). The plugin lacks proper CSRF token validation, enabling attackers to inject persistent malicious scripts through sitemap configuration endpoints.

MitigationUpdate the Google XML News Sitemap plugin to a patched version that implements CSRF token validation and proper input sanitization; if no patch is available, disable the plugin until a fix is released.

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. Verify the Google XML News Sitemap plugin is installed
    Access WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Google XML News Sitemap' or 'gn-xml-sitemap' in the list of active plugins
    Affected if the plugin appears in the list of installed plugins (either active or inactive)
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name to view details, or open the main plugin file (typically gn-xml-sitemap.php) and locate the version in the plugin header comment
    Affected if the version displayed is earlier than the patched release (compare against the latest version on WordPress.org or the version noted in security advisories)
  3. Inspect sitemap configuration endpoints for CSRF protection
    Examine the plugin PHP source code for form submissions and AJAX actions, specifically looking for wp_nonce_field, wp_verify_nonce, or check_admin_referer function calls in files handling sitemap settings (commonly functions.php, admin.php, or a settings class file)
    Affected if form handlers or settings update endpoints lack CSRF token validation (nonce checks are missing or not properly implemented)
  4. Check for stored XSS in sitemap settings
    In WordPress admin, navigate to the plugin settings page (usually under Settings > XML News Sitemap or similar), inspect the HTML source of configuration forms for any unescaped output of user-supplied values, or review stored options in wp_options table where plugin settings are saved
    Affected if plugin settings fields accept and store unsanitized input that could contain malicious scripts, or if saved settings contain unexpected script tags
  5. Verify if the vulnerability is exploitable
    Attempt a low-risk test by submitting a configuration request (via browser developer tools or a testing tool) without a valid CSRF token; observe whether the request is rejected or accepted without token validation
    Affected if the plugin processes configuration updates without requiring a valid CSRF token, allowing forged requests to succeed

You are affected if the Google XML News Sitemap plugin is installed, the version lacks CSRF protection in its configuration endpoints, and the plugin processes settings updates without proper token validation.

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 the Google XML News Sitemap plugin to a patched version that implements CSRF token validation and proper input sanitization; if no patch is available, disable the plugin until a fix is released.

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-48304 — 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-48304 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