Security readout for executives and security teams
Plain-English summary
CVE-2025-23803 affects the WordPress Snippy plugin through version 1.4.1. The reported issue is CSRF that can lead to reflected XSS, meaning a targeted user could be tricked into causing script execution in a WordPress context. The bundle does not identify active exploitation or a confirmed fixed version.
Executive priority
Treat as a high-priority WordPress plugin exposure, especially on public or business-critical sites. The main business concern is account-context script execution after user interaction. Act quickly on inventory and vendor guidance, but do not assume active exploitation from the provided evidence.
Technical view
The CVE describes CWE-352 CSRF in Rik Schennink Snippy, with reflected XSS impact. CVSS 3.1 is 7.1 high: network attack vector, low complexity, no privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites using the Snippy plugin at versions up to and including 1.4.1. The source bundle contains limited affected-version metadata, so asset validation should rely on installed plugin inventory, not CPE matching.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no source supplied here states active exploitation. User interaction is required by the CVSS vector, so realistic risk is targeted phishing or lure-based abuse against WordPress users.
Researcher notes
Evidence is narrow: CVE metadata and Patchstack VDB reference identify CSRF to reflected XSS through Snippy 1.4.1. The bundle does not provide exploit details, proof of exploitation, or a named patch. Avoid claiming broader WordPress impact beyond this plugin.
Mitigation direction
- Inventory WordPress sites for the Snippy plugin and installed version.
- Check Patchstack, WordPress, or vendor guidance for a fixed version or workaround.
- Disable or remove Snippy where it is not business-critical.
- Prioritize sites with administrative users exposed to untrusted links.
- Review WordPress security controls for CSRF and XSS hardening.
Validation and detection
- Confirm whether Snippy is installed on each WordPress property.
- Record the installed version and compare it with <= 1.4.1 exposure.
- Review plugin changelogs or vendor advisories for remediation status.
- Check web logs and security alerts for suspicious WordPress user activity.
- Verify compensating controls without performing exploit reproduction.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-23803 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/snippy/vulnerability/wordpress-snippy-plugin-1-4-1-csrf-to-cross-site-scripting-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.