Security readout for executives and security teams
Plain-English summary
A WordPress plugin called Better Protected Pages is reported vulnerable through version 1.0. A malicious site could trick a logged-in user into making an unwanted change that stores script content. That could affect site integrity, visitor trust, and administrative control depending on where the script runs.
Executive priority
Treat this as a high-priority WordPress plugin exposure for any affected site. Prioritize inventory first, then remove, disable, or update based on vendor guidance. Urgency increases for public sites, sites with many administrators, or sites supporting customer trust and lead generation.
Technical view
The issue is categorized as CSRF, CWE-352, with impact described as Stored XSS. The CVSS 3.1 score is 7.1 high, vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. Public data identifies madeglobal Better Protected Pages, package better-protected-pages, through <= 1.0.
Likely exposure
Exposure is likely limited to WordPress sites that installed Better Protected Pages version 1.0 or earlier. The provided structured affected data is sparse, so teams should verify by plugin slug and installed version rather than relying only on CPE matching.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The attack requires user interaction, consistent with CSRF, and could result in stored XSS if a trusted user is tricked while authenticated.
Researcher notes
Evidence is concise and mostly advisory-level. The record names CSRF enabling Stored XSS but does not provide detailed vulnerable endpoints, patch version, or exploitation evidence in the supplied bundle. Avoid assuming exploit availability or a specific remediation beyond vendor guidance.
Mitigation direction
- Inventory WordPress sites for the better-protected-pages plugin.
- Check Patchstack and vendor guidance for a fixed supported release.
- Update only to a vendor-approved fixed version when available.
- Disable or remove the plugin if no supported fix exists.
- Restrict administrative access and reinforce session hygiene for WordPress users.
Validation and detection
- Confirm installed plugin name, slug, and version on every WordPress site.
- Compare findings against Patchstack and CVE records for CVE-2025-23875.
- Review WordPress content and settings for unexpected script-bearing changes.
- Check whether the plugin remains required for business workflows.
- Document compensating controls if the plugin cannot be removed promptly.
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-23875 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.