Security readout for executives and security teams
Plain-English summary
This vulnerability affects WooCommerce sites using the Stripe Payment Gateway plugin at vulnerable versions. An unauthenticated attacker could access other users' payment-related personal information through an object access control flaw. The main business risk is customer PII disclosure, not payment processing disruption or system takeover based on the provided sources.
Executive priority
Treat as a high-priority e-commerce privacy issue. It does not indicate takeover in the provided evidence, but unauthenticated PII disclosure can create customer trust, regulatory, and incident-response impact.
Technical view
CVE-2023-34000 is an unauthenticated IDOR in WooCommerce Stripe Payment Gateway plugin versions up to 7.4.0. It maps to CWE-639 and has CVSS 3.1 score 7.5, with network access, low complexity, no privileges, no user interaction, and high confidentiality impact only.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce stores with the WooCommerce Stripe Payment Gateway plugin installed at version 7.4.0 or earlier. The bundle does not identify other affected products or platforms.
Exploitation context
The source bundle does not show CISA KEV listing, and no provided source states active exploitation. Risk remains material because the issue is unauthenticated, remotely reachable, and tied to PII disclosure.
Researcher notes
Provided evidence is limited to the CVE record and Patchstack references. Avoid assuming active exploitation, exact fixed version, or affected data fields unless confirmed from vendor or advisory text.
Mitigation direction
- Identify all WordPress sites using WooCommerce Stripe Payment Gateway.
- Check whether installed plugin versions are 7.4.0 or earlier.
- Update to a vendor-confirmed fixed version before returning normal operation.
- If immediate update is unavailable, consider disabling the plugin temporarily.
- Review WooCommerce, Patchstack, and CVE guidance for any newly published remediation details.
Validation and detection
- Inventory plugin name and version across production and staging WordPress sites.
- Confirm no site remains on WooCommerce Stripe Payment Gateway 7.4.0 or earlier.
- Verify remediation against WooCommerce or Patchstack advisory guidance.
- Review access logs for unusual unauthenticated requests to payment or order-related paths.
- Assess whether customer PII exposure notification obligations require internal review.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-34000 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/vulnerability/woocommerce-gateway-stripe/wordpress-woocommerce-stripe-payment-gateway-plugin-7-4-0-insecure-direct-object-references-idor-vulnerability?_s_id=cveCVE reference · vdb-entry
- https://patchstack.com/articles/unauthenticated-idor-to-pii-disclosure-vulnerability-in-woocommerce-stripe-gateway-plugin?_s_id=cveCVE reference · technical-description, third-party-advisory
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.