Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress OOPSpam Anti-Spam plugin through version 1.1.44. It is a CSRF issue, meaning an attacker may be able to trick a logged-in WordPress user into making an unintended plugin-related change. The impact is limited to integrity, and the sources do not show active exploitation.
Executive priority
Treat as a normal-priority web application hygiene issue, not an emergency. Prioritize internet-facing WordPress sites and administrator-heavy environments, but the published score and lack of KEV evidence suggest moderate urgency.
Technical view
CVE-2023-35913 is a CWE-352 cross-site request forgery vulnerability in OOPSpam Anti-Spam for WordPress, reported for versions up to 1.1.44. CVSS 3.1 is 4.3 with network access, low complexity, no attacker privileges, required user interaction, and low integrity impact only.
Likely exposure
Exposure is likely limited to WordPress sites that installed OOPSpam Anti-Spam version 1.1.44 or earlier. Risk is higher where privileged WordPress users remain logged in while browsing untrusted sites.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not claim active exploitation. Successful abuse requires user interaction and depends on a victim with relevant WordPress access being induced to trigger an unwanted request.
Researcher notes
The source bundle confirms CSRF, affected plugin identity, version threshold, CWE, and CVSS. It does not provide endpoint details, proof of concept, exploit activity, or a named fixed version, so validation should stay focused on asset inventory and vendor advisory review.
Mitigation direction
- Inventory WordPress sites for the OOPSpam Anti-Spam plugin and installed version.
- Check OOPSpam or Patchstack guidance for the supported fixed version.
- Upgrade the plugin if a vendor-supported fixed release is available.
- Disable or remove the plugin if no safe version can be confirmed.
- Limit WordPress administrator sessions to trusted devices and networks where practical.
Validation and detection
- Confirm whether OOPSpam Anti-Spam is installed on each WordPress instance.
- Record plugin versions and flag any at or below 1.1.44.
- Review recent WordPress admin activity for unexpected plugin configuration changes.
- Verify remediation by rechecking plugin version after update or removal.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2023-35913 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.