Security readout for executives and security teams
Plain-English summary
CVE-2025-23902 affects the WordPress Error Notification plugin through version 0.2.7. A CSRF weakness can lead to stored cross-site scripting, meaning a user interaction could cause malicious content to be saved and later run in a browser. The source bundle does not name active exploitation or a fixed version.
Executive priority
Treat as a high-priority WordPress plugin exposure if the plugin is present. The business urgency comes from stored XSS potential on public web properties, but the current source bundle does not prove active exploitation or provide a named patch.
Technical view
The issue is reported as CWE-352 CSRF in Taras Dashkevych Error Notification for WordPress through 0.2.7, with stored XSS impact. CVSS 3.1 is 7.1, network reachable, low complexity, no attacker privileges, user interaction required, and changed scope with low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations running the Error Notification plugin at version 0.2.7 or earlier. Sites not using this plugin are not indicated as affected. The provided affected-version metadata is sparse, so confirm against installed plugin inventory and vendor records.
Exploitation context
The source bundle does not cite KEV listing or active exploitation. The CVSS vector indicates user interaction is required, and the reported outcome is stored XSS following CSRF. Public evidence here does not describe the exact vulnerable action, victim role, or execution location.
Researcher notes
Evidence is sufficient for classification as CSRF leading to stored XSS, but incomplete for root cause, vulnerable endpoint, exploit prerequisites beyond UI:R, and fixed-version status. Avoid assuming exploitability details not present in the CVE or Patchstack reference.
Mitigation direction
- Inventory WordPress sites for the Error Notification plugin and installed version.
- Check Patchstack and vendor guidance for a fixed release or official mitigation.
- If no fix is available, consider disabling or removing the plugin after impact review.
- Limit access to WordPress administrative functions using existing access controls.
- Increase monitoring for unexpected stored content or script-like changes.
Validation and detection
- Confirm whether Error Notification is installed on each WordPress instance.
- Record plugin versions and flag any version 0.2.7 or earlier.
- Review CVE and Patchstack records for updated remediation status.
- Validate remediation through safe configuration review or non-production testing.
- Check logs and content changes for suspicious stored script activity.
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-23902 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/error-notification/vulnerability/wordpress-error-notification-plugin-0-2-7-csrf-to-stored-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.