Security readout for executives and security teams
Plain-English summary
This vulnerability affects the Stripe Payments for WooCommerce plugin by Checkout Plugins up to version 1.4.10. A malicious site could trick a logged-in WordPress user into causing plugin settings to change. The known impact is limited integrity impact, not data theft or service outage.
Executive priority
Treat this as a routine but real e-commerce site hardening item. It is not described as actively exploited, but unauthorized payment-plugin setting changes can create operational risk and should be cleared during normal vulnerability remediation cycles.
Technical view
CVE-2023-23865 is a CWE-352 CSRF issue in checkout-plugins-stripe-woo <= 1.4.10. The CVSS 3.1 score is 4.3, with network access, low attack complexity, no attacker privileges, required user interaction, and low integrity impact. Sources describe the consequence as settings change.
Likely exposure
Exposure is likely limited to WordPress sites running Stripe Payments For WooCommerce by Checkout Plugins version 1.4.10 or earlier. Sources do not identify hosting-specific exposure, affected WooCommerce versions, or exact required victim role.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction, consistent with a CSRF scenario where a victim is induced to trigger an unintended settings change.
Researcher notes
Evidence is narrow: the CVE and Patchstack reference identify CSRF leading to settings change, but do not provide exploit details, fixed version, or detailed prerequisites in the supplied bundle. Avoid assuming broader payment compromise without additional vendor evidence.
Mitigation direction
- Identify whether checkout-plugins-stripe-woo is installed and record the version.
- Check the vendor or Patchstack entry for fixed-version guidance.
- Update the plugin if a fixed version is available from the vendor.
- Disable or remove the plugin if it is unused or cannot be safely updated.
- Limit privileged WordPress sessions and avoid untrusted links while administering the site.
Validation and detection
- Confirm plugin presence and version on each WordPress site.
- Review plugin settings for unexpected changes.
- Check WordPress administrative logs for settings changes after February 28, 2023.
- Document non-exposure where the plugin is absent or newer than 1.4.10.
- Monitor vendor and Patchstack advisories for remediation status.
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-23865 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
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.