Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress Rich Text Editor plugin installation could let an attacker trick an authenticated site user into making a change that stores malicious script in the site. The issue requires user interaction but can persist once saved, creating risk for visitors or administrators who later view affected content.
Executive priority
Treat as a high-priority WordPress exposure review, especially for public sites or sites with many administrators. Prioritize inventory, version confirmation, and vendor guidance before disruption-heavy remediation.
Technical view
CVE-2025-31623 is a CSRF vulnerability leading to stored XSS in richtexteditor Rich Text Editor for WordPress through version 1.0.1. CVSS 3.1 is 7.1 high: network exploitable, low complexity, no attacker privileges, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running the Rich Text Editor plugin at version 1.0.1 or earlier. The bundle has inconsistent affected-version metadata, so teams should verify installed plugin identity and version directly against vendor or Patchstack records.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source here confirms active exploitation. The attack pattern requires tricking a user into an unintended action, then stored XSS may execute when affected stored content is viewed.
Researcher notes
Evidence supports CSRF to stored XSS, but the bundle does not include a fixed version, exploit details, or proof of active exploitation. Avoid assuming broader Rich Text Editor products are affected beyond the WordPress plugin identified by the sources.
Mitigation direction
- Inventory WordPress sites for the Rich Text Editor plugin.
- Check Patchstack or vendor guidance for a fixed release.
- Update if a fixed version is available from trusted sources.
- Disable or remove the plugin where no fix is confirmed.
- Restrict administrative access and review CSRF protections around plugin settings.
Validation and detection
- Confirm whether any site runs Rich Text Editor version 1.0.1 or earlier.
- Verify plugin slug/package identity as richtexteditor before scoping impact.
- Review stored plugin-managed content for unexpected script-like changes.
- Check WordPress admin activity around suspicious content or settings changes.
- Document compensating controls if the plugin cannot be removed.
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-31623 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.
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.7Primary CVE scoreVulnerability 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
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.