Security Resilience

CVE-2025-23803

CSRF

Published
22 January 2025
Modified
23 April 2026
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
EPSS Score 0.0017 6th percentile
Risk Priority 50 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-23803 is a high-severity CSRF (CWE-352) vulnerability. Its CVSS base score is 7.1 (High).

Operationally, ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-23803 is a Cross-Site Request Forgery (CSRF) vulnerability in the Snippy WordPress plugin developed by Rik Schennink. The issue affects Snippy versions from n/a through 1.4.1 and enables Reflected Cross-Site Scripting (XSS). Published on 2025-01-22, it carries a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) and maps to CWE-352.

Remote attackers require no privileges to exploit this vulnerability, but user interaction is necessary, such as an authenticated victim visiting a malicious site. The attacker can craft a webpage that forges a CSRF request to the Snippy plugin, triggering reflected XSS in the user's browser. This changes the scope of impact, allowing limited confidentiality, integrity, and availability effects, such as potential session token theft or malicious script execution within the plugin's context.

The Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/snippy/vulnerability/wordpress-snippy-plugin-1-4-1-csrf-to-cross-site-scripting-xss-vulnerability?_s_id=cve provides details on the CSRF-to-XSS vulnerability in Snippy version 1.4.1 for WordPress. Security practitioners should consult this reference for recommended mitigations.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Cross-Site Request Forgery (CSRF) vulnerability in Rik Schennink Snippy snippy allows Reflected XSS.This issue affects Snippy: from n/a through <= 1.4.1.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-13560Shared CWE-352
CVE-2025-31921Shared CWE-352
CVE-2025-31457Shared CWE-352
CVE-2023-34033Shared CWE-352
CVE-2024-2960Shared CWE-352
CVE-2024-35009Shared CWE-352
CVE-2024-6136Shared CWE-352
CVE-2024-12003Shared CWE-352
CVE-2024-37431Shared CWE-352
CVE-2025-58869Shared CWE-352

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

References