Security readout for executives and security teams
Plain-English summary
WordPress sites using Content Security Policy Pro through version 1.3.5 may be vulnerable. The issue is CSRF that can lead to stored XSS if a logged-in user is tricked into interacting with attacker-controlled content. Sources do not identify confirmed exploitation or a specific fixed release.
Executive priority
Prioritize remediation for public WordPress sites using this plugin, especially business-critical or high-traffic properties. The issue can affect page integrity and user trust, but active exploitation is not confirmed in the provided sources.
Technical view
CVE-2025-23820 is a CWE-352 CSRF issue in thapa.laxman Content Security Policy Pro. The title indicates CSRF to stored XSS. CVSS 3.1 is 7.1, network-reachable, low complexity, no attacker privileges, and requires user interaction with changed scope.
Likely exposure
Exposure is limited to WordPress installations with Content Security Policy Pro installed at version 1.3.5 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.
Exploitation context
The CVSS vector requires user interaction and no attacker privileges. The source bundle does not show CISA KEV listing or other evidence of active exploitation, so exploitation should be treated as possible but unconfirmed.
Researcher notes
The bundle identifies CSRF and stored XSS impact but does not provide root-cause details, affected endpoint names, proof of concept, or fixed-version metadata. Avoid assuming broader WordPress or plugin ecosystem impact beyond Content Security Policy Pro through 1.3.5.
Mitigation direction
- Inventory WordPress sites for Content Security Policy Pro and record installed versions.
- Check Patchstack, CVE, and vendor guidance for a fixed release or official mitigation.
- Update or remove affected plugin versions when vendor guidance supports that action.
- Limit WordPress administrator exposure and enforce strong session hygiene.
- Review recent plugin setting changes for unauthorized or unexpected modifications.
Validation and detection
- Confirm whether content-security-policy-pro is installed on each WordPress site.
- Verify installed plugin versions against the affected range: through 1.3.5.
- Check whether any official vendor or Patchstack remediation has been published.
- Review security logs for suspicious administrator actions around plugin settings.
- Confirm compensating controls do not rely on this plugin alone.
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-23820 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
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.