Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress Add RSS plugin installation could be abused through CSRF to store malicious script in the site. A victim must interact with attacker-controlled content, but the result can affect confidentiality, integrity, and availability at a limited level. This matters most for WordPress sites still running Add RSS version 1.5 or earlier.
Executive priority
Treat this as a high-priority WordPress plugin exposure check, not an emergency exploitation event. Prioritize public or business-critical WordPress sites first, especially where plugin inventory is weak.
Technical view
CVE-2025-23895 is a CSRF issue in Dan Cameron Add RSS for WordPress, reported as affecting versions through 1.5. The described impact is stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no attacker privileges, required user interaction, and changed scope.
Likely exposure
Exposure is limited to WordPress sites using the Add RSS plugin at version 1.5 or earlier. The source bundle does not identify affected CPEs or a fixed version.
Exploitation context
The bundle marks CISA KEV status as false, and no cited source states active exploitation. Exploitation requires user interaction, consistent with the CVSS vector and CSRF-to-stored-XSS description.
Researcher notes
Evidence is narrow: CVE and Patchstack identify CSRF leading to stored XSS in Add RSS through 1.5. The bundle does not provide proof-of-concept details, exploitation telemetry, or a named fixed release. Avoid assuming broader Dan Cameron products are affected.
Mitigation direction
Inventory WordPress sites for the Add RSS plugin and version.
Check Patchstack and vendor guidance for fixed versions or official remediation.
Update the plugin if a maintained fixed release is available.
Disable or remove the plugin where no trusted fix is available.
Review WordPress administrative access and session hygiene.
Validation and detection
Confirm whether Add RSS is installed on each WordPress site.
Record installed plugin versions and flag version 1.5 or earlier.
Review plugin-managed RSS settings or stored content for unexpected script content.
Check relevant WordPress logs for suspicious administrative changes.
Document compensating controls if the plugin cannot be removed quickly.
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.