Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the WooCommerce PayPal Payments WordPress plugin through version 2.0.4. A victim would need to be tricked into interacting while authenticated. The published impact is limited to integrity, not data theft or service outage.
Executive priority
Treat this as a routine but real e-commerce hardening item. It is not supported as actively exploited in the sources, but exposed payment-related plugin administration should be remediated promptly to reduce transaction and configuration risk.
Technical view
CVE-2023-35917 is CWE-352 affecting package woocommerce-paypal-payments. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact. The exact vulnerable action is not described in the provided sources.
Likely exposure
Exposure is limited to WordPress/WooCommerce sites running WooCommerce PayPal Payments version 2.0.4 or earlier. Sites without this plugin, or not on the affected versions, are not indicated as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Successful abuse requires user interaction and likely depends on an authenticated administrator or privileged user being induced to trigger an unwanted action.
Researcher notes
Available public detail is sparse. The source bundle identifies CSRF, affected plugin and version boundary, CWE-352, and CVSS characteristics, but does not specify the vulnerable endpoint, nonce failure, affected administrative action, or fixed release details.
Mitigation direction
- Inventory WordPress sites for WooCommerce PayPal Payments plugin versions.
- Upgrade away from version 2.0.4 or earlier using official vendor guidance.
- Restrict WordPress administrator access to trusted users only.
- Review vendor and Patchstack guidance before applying compensating controls.
- Prioritize remediation on revenue-generating WooCommerce stores.
Validation and detection
- Confirm whether woocommerce-paypal-payments is installed on each WordPress site.
- Record the installed plugin version and compare it to <= 2.0.4.
- Check WordPress admin or audit logs for unexpected plugin configuration changes.
- Verify remediation by confirming the plugin is no longer on an affected version.
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-35917 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.