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

CVE-2025-46452

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
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 Olav Kolbu Google News allows Stored XSS. This issue affects Google News: from n/a through 2.5.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

CSRF vulnerability in the Google News plugin allows authenticated administrators to be tricked into submitting malicious requests that inject and store XSS payloads in plugin settings or output. Attackers exploit the lack of CSRF token validation to perform store malicious scripts that execute when users view affected pages.

MitigationImplement anti-CSRF tokens on all state-changing forms and validate Origin/Referer headers; apply available patch from vendor; sanitize and escape all user inputs and dynamically rendered content.

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 Google News plugin is installed
    Access your CMS plugin management interface or inspect the plugins directory to confirm the Google News plugin is present
    Affected if The plugin is not installed means not affected
  2. Determine installed plugin version
    Check the plugin header or version file (typically in plugin root directory) to identify the exact version number
    Affected if Version is unpatched and matches the vulnerable version range for this CVE
  3. Inspect plugin settings for suspicious content
    Access the Google News plugin settings pages in the admin panel; examine all configuration fields, especially those that store and display user-supplied values, for unexpected script tags, iframe elements, or encoded JavaScript
    Affected if Any XSS payloads are found stored in plugin configuration fields
  4. Check plugin forms for CSRF protection
    Examine the plugin PHP source code for forms handling state-changing operations; look for nonce verification, CSRF tokens, or validation of Origin/Referer headers
    Affected if Forms lack CSRF token validation and nonce checks on state-changing actions

The environment is affected if the Google News plugin is installed and running an unpatched version, or if the plugin settings contain injected XSS payloads due to missing CSRF protection.

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 tokens on all state-changing forms and validate Origin/Referer headers; apply available patch from vendor; sanitize and escape all user inputs and dynamically rendered content.

Recommended fix Moderate confidence

Version greater than 2.5.1 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Google News' plugin by Olav Kolbu
  4. 4. Check if an update is available for this plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. If no automatic update appears, manually download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is functioning correctly and test that the CSRF vulnerability is no longer exploitable

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

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