Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in pedjas Stop Comment Spam stop-comment-spam allows Stored XSS.This issue affects Stop Comment Spam: from n/a through <= 0.5.3.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23826 is a high-severity stored cross-site scripting issue in the WordPress Stop Comment Spam plugin through version 0.5.3. A successful attack could let malicious script persist in a site context after user interaction, creating risk to site integrity, visitor trust, and administrative sessions.
Executive priority
Prioritize this for WordPress properties that use the plugin, especially public or business-critical sites. It is high severity, but current sources do not support emergency treatment based on known active exploitation.
Technical view
The CVE describes CWE-79 improper output neutralization in pedjas Stop Comment Spam, package stop-comment-spam, affecting versions through 0.5.3. Patchstack labels it CSRF to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Stop Comment Spam plugin installed at version 0.5.3 or earlier. The provided sources do not identify affected endpoints, default install counts, or whether a fixed version exists.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. Exploitation requires user interaction, and Patchstack characterizes the path as CSRF to stored XSS, but the public bundle does not provide reproduction details.
Researcher notes
Evidence is sparse. The bundle confirms stored XSS, CSRF-to-XSS characterization, CVSS vector, and affected version range, but not the vulnerable parameter, endpoint, exploit maturity, or fixed release. Avoid assuming broader WordPress impact beyond this plugin.
Mitigation direction
Inventory WordPress sites for the Stop Comment Spam plugin and version.
Treat version 0.5.3 or earlier as vulnerable until vendor guidance says otherwise.
Check Patchstack and vendor channels for a fixed version or official mitigation.
Disable or remove the plugin where business impact is acceptable.
Restrict WordPress admin access and reinforce anti-phishing controls for privileged users.
Validation and detection
Confirm whether stop-comment-spam is installed on each WordPress site.
Record installed plugin version and compare it with the affected range through 0.5.3.
Review vendor or Patchstack advisories for remediation status before closure.
Inspect pages and plugin-managed content for unexpected stored script or HTML.
Verify compensating controls without attempting offensive reproduction.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.