CVE-2025-23605: WordPress Call To Action Popup plugin <= 1.0.2 - Reflected Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in lampd Call To Action Popup call-to-action-popup allows Reflected XSS.This issue affects Call To Action Popup: from n/a through <= 1.0.2.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23605 affects the WordPress Call To Action Popup plugin through version 1.0.2. It is a reflected XSS issue: a victim must interact with a crafted request for browser-side script execution. Business risk is highest for public WordPress sites using this plugin, especially where administrators or customers may follow untrusted links.
Executive priority
Treat as a high-priority WordPress hygiene issue for public sites. Prioritize sites with administrator traffic, customer-facing pages, or high brand impact, but do not represent it as known actively exploited based on the provided evidence.
Technical view
The issue is CWE-79 improper neutralization during page generation in lampd Call To Action Popup. CVSS 3.1 is 7.1, with network attack vector, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress installations running the Call To Action Popup plugin at version 1.0.2 or earlier. The bundle does not identify affected URLs, vulnerable parameters, install prevalence, or a confirmed fixed version.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The CVSS vector indicates remote exploitation is possible without authentication, but user interaction is required. No exploit details are provided in the allowed sources.
Researcher notes
Evidence supports reflected XSS classification and CVSS scoring, but not exploitation in the wild, affected endpoint details, or a fixed version. Avoid assumptions beyond Call To Action Popup through 1.0.2 unless vendor or Patchstack details confirm more.
Mitigation direction
Inventory WordPress sites for the Call To Action Popup plugin and version.
Check vendor or Patchstack guidance for an official fixed version or advisory.
Disable or remove the plugin where business impact is acceptable.
Use WAF and browser hardening as compensating controls, not confirmed fixes.
Validation and detection
Confirm whether each WordPress site has call-to-action-popup installed.
Record plugin versions and flag 1.0.2 or earlier for remediation.
Review web logs for unusual requests to plugin-controlled pages.
Verify remediation by confirming the plugin is removed, disabled, or officially fixed.
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.