CVE-2025-23745: WordPress Call me Now plugin <= 1.0.5 - CSRF to Stored XSS vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in Tussendoor B.V. Call me Now call-me-now allows Stored XSS.This issue affects Call me Now: from n/a through <= 1.0.5.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23745 affects the WordPress Call me Now plugin through version 1.0.5. A victim can be tricked into causing a stored cross-site scripting change. That could let malicious script persist in the site and affect users who later view the impacted content.
Executive priority
Treat as a high-priority WordPress plugin exposure. It is not confirmed exploited in the provided sources, but stored XSS can create persistent business risk on public websites. Prioritize inventory and removal or update decisions.
Technical view
The public record describes a CSRF issue leading to stored XSS in Tussendoor B.V. Call me Now, package call-me-now, through version 1.0.5. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, and user interaction required.
Likely exposure
Exposure is limited to WordPress sites with the Call me Now plugin installed at version 1.0.5 or earlier. Risk is higher where administrators remain authenticated while browsing untrusted content.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires user interaction and appears to rely on CSRF to store XSS content. Public exploit maturity is not established in the source bundle.
Researcher notes
Evidence is concise and vendor-specific. The key uncertainty is remediation status; the source bundle names affected versions but does not name a fixed release. Avoid assuming broader WordPress impact beyond this plugin and version range.
Mitigation direction
Inventory WordPress sites for Call me Now plugin version 1.0.5 or earlier.
Check vendor, WordPress plugin, and Patchstack guidance for a fixed version.
If no fixed version is available, disable or remove the plugin.
Limit administrative sessions and avoid browsing untrusted sites while authenticated.
Monitor affected sites for unauthorized plugin configuration or content changes.
Validation and detection
Confirm whether the call-me-now plugin is installed and enabled.
Record installed plugin versions across production and staging sites.
Review Patchstack and CVE records for any updated remediation guidance.
Inspect affected sites for unexpected stored content or plugin setting changes.
Check security monitoring for suspicious administrator-initiated changes.
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.