Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in promoz73 Exit Popup Free exit-popup-free allows Stored XSS.This issue affects Exit Popup Free: from n/a through <= 1.0.
Security readout for executives and security teams
Plain-English summary
CVE-2025-31591 is stored XSS in the Exit Popup Free WordPress plugin through version 1.0. A highly privileged user could save unsafe input that later runs in another user's browser. Impact is limited but can affect confidentiality, integrity, and availability in the WordPress context.
Executive priority
Treat as a targeted WordPress hygiene issue, not an emergency internet-wide exposure based on current evidence. Prioritize sites with multiple administrators, untrusted content managers, or sensitive authenticated users.
Technical view
The issue is CWE-79 improper neutralization during web page generation. CVSS 3.1 score is 5.9 with AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L. It is network-reachable, low complexity, requires high privileges and user interaction, and changes scope.
Likely exposure
Exposure appears limited to WordPress sites running promoz73 Exit Popup Free, package exit-popup-free, from unspecified earlier versions through 1.0. The source bundle does not identify affected CPEs or a fixed version.
Exploitation context
No active exploitation is cited. The CVE is not listed as KEV in the supplied data. Exploitation requires high privileges and a victim interaction path, reducing broad drive-by risk but leaving shared-admin WordPress environments exposed.
Researcher notes
Evidence is limited to CVE metadata and the Patchstack database reference. The supplied data does not include payload details, affected code paths, public exploit confirmation, or a named patched version.
Mitigation direction
Inventory WordPress sites for the exit-popup-free plugin through version 1.0.
Check Patchstack and vendor guidance for fixed versions or official mitigation.
Disable or remove the plugin where it is unused or cannot be safely fixed.
Restrict WordPress administrative access to trusted users only.
Review stored plugin content for unexpected script-like changes.
Validation and detection
Confirm installed plugin slug is exit-popup-free and record its version.
Verify whether any installation is version 1.0 or earlier.
Review WordPress roles with permission to edit plugin-managed content or settings.
Check logs and content history for suspicious privileged edits.
Document whether vendor guidance names a fixed release or workaround.
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-79: 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.