Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress plugin can let an attacker trick a logged-in user into making a change that stores malicious script on the site. That script may later run in another user’s browser. The issue is high severity, but the supplied sources do not show active exploitation.
Executive priority
Treat this as a high-priority WordPress plugin exposure if Script Compressor is present. It is not KEV-listed in the supplied data, so prioritize based on confirmed plugin use and public site importance.
Technical view
CVE-2025-31391 is a CSRF flaw in the regen Script Compressor WordPress plugin through version 1.7.1, leading to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges required, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites running the Script Compressor plugin through version 1.7.1. The supplied sources do not identify other affected products, CPEs, or hosted services.
Exploitation context
The sources describe CSRF to stored XSS and mark KEV as false. No supplied source states active exploitation. Successful abuse requires user interaction and can affect confidentiality, integrity, and availability at low impact levels under the CVSS vector.
Researcher notes
Evidence is narrow: CVE data and Patchstack identify CSRF leading to stored XSS through 1.7.1. The bundle does not provide exploit details, proof of exploitation, or a named fixed version.
Mitigation direction
Inventory WordPress sites for the Script Compressor plugin and installed version.
Check Patchstack and vendor guidance for a fixed version or official mitigation.
Disable or remove the plugin where it is not business-critical.
Prioritize remediation on public or administrator-used WordPress sites.
Review site content and plugin settings for unexpected stored scripts.
Validation and detection
Confirm whether Script Compressor is installed and active on each WordPress site.
Record plugin versions and flag any deployment through 1.7.1.
Review administrative pages and stored plugin output for unexpected script content.
Check security advisories before deciding whether upgrade, removal, or compensating controls apply.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
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.