Security readout for executives and security teams
Plain-English summary
A WordPress payment plugin used by WooCommerce sites could let an unauthenticated attacker change or act on data they should not control, because object access is based on user-controlled keys. For ecommerce sites, the business risk is unauthorized manipulation of payment-related plugin objects. The cited sources identify affected versions through 7.6.1; they do not prove active exploitation.
Executive priority
Treat this as a high-priority ecommerce integrity risk. It affects a payment gateway plugin and requires no attacker login per the CVSS vector. Start with internet-facing stores and confirm whether any still run affected versions.
Technical view
CVE-2023-51502 is a CWE-639 IDOR/authorization bypass in WooCommerce Stripe Payment Gateway (woocommerce-gateway-stripe) through 7.6.1. CVSS 3.1 is 7.5: network, low complexity, no privileges, no user interaction, unchanged scope, high integrity impact only. The bundle does not include endpoint-level details, exploit procedure, or a named fixed release.
Likely exposure
Exposure is likely on internet-facing WordPress stores using WooCommerce Stripe Payment Gateway version 7.6.1 or earlier. Sites without the plugin, or with versions outside the affected range per vendor guidance, are not indicated as affected by the provided sources.
Exploitation context
The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation. The CVSS vector still indicates a remotely reachable, unauthenticated, low-complexity issue with high integrity impact, so vulnerable ecommerce sites should treat it as urgent even without confirmed exploitation.
Researcher notes
The available evidence identifies the weakness class, affected plugin, affected range, and CVSS vector, but not precise vulnerable endpoints, exploit status, or a fixed release. Avoid assumptions beyond version exposure and validate against vendor or Patchstack data before closing findings.
Mitigation direction
- Inventory all WordPress sites for woocommerce-gateway-stripe and record installed versions.
- Prioritize sites running WooCommerce Stripe Payment Gateway 7.6.1 or earlier.
- Check WooCommerce or Patchstack guidance for the fixed version and upgrade when confirmed.
- If no fix is available, assess temporary plugin disablement against payment continuity needs.
- Monitor payment workflow and application logs for unauthorized object changes.
Validation and detection
- Confirm whether each WooCommerce site has WooCommerce Stripe Payment Gateway installed.
- Verify the installed plugin version is not 7.6.1 or earlier.
- Review vulnerability scanner results for CVE-2023-51502 on WordPress assets.
- Check change records to confirm remediation was applied across production and staging.
- Review logs for suspicious unauthenticated activity affecting payment-related objects.
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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-51502 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:N/I:H/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:N/I:H/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:N/I:H/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.
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.