LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35049: WordPress WooCommerce Stripe Payment Gateway plugin <= 7.4.0 - Unauthenticated Broken Access Control vulnerability

Missing Authorization vulnerability in WooCommerce WooCommerce Stripe Payment Gateway.This issue affects WooCommerce Stripe Payment Gateway: from n/a through 7.4.0.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WooCommerce Stripe Payment Gateway plugin versions through 7.4.0. An unauthenticated attacker could reach functionality that should require authorization and cause unauthorized integrity changes. For stores using this plugin, the business concern is payment-related workflow integrity, not confirmed data theft from the supplied sources.

Executive priority

Treat this as a high-priority e-commerce remediation item for any WooCommerce store using the Stripe gateway plugin. Prioritize inventory and vendor-guided updating because the issue may allow unauthorized integrity changes without login.

Technical view

CVE-2023-35049 is a CWE-862 missing authorization issue in the WordPress WooCommerce Stripe Payment Gateway plugin through 7.4.0. The CVSS 3.1 score is 7.5 with network attack vector, no privileges, no user interaction, and high integrity impact.

Likely exposure

Exposure is most likely on public WordPress/WooCommerce sites running WooCommerce Stripe Payment Gateway version 7.4.0 or older. The source bundle does not identify specific vulnerable endpoints, configurations, or hosting conditions beyond the affected plugin range.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation. The vulnerability is still serious because it is unauthenticated, network-reachable, low-complexity, and affects integrity.

Researcher notes

Available sources identify missing authorization and affected versions through 7.4.0 but do not provide endpoint details, exploit prerequisites beyond unauthenticated access, proof-of-concept status, or a named fixed version. Avoid assuming exploitability details beyond the CVSS vector and CWE.

Mitigation direction

  • Inventory WooCommerce sites for WooCommerce Stripe Payment Gateway versions through 7.4.0.
  • Check WooCommerce and Patchstack guidance for the fixed or recommended plugin version.
  • Update the plugin beyond the affected range when vendor guidance confirms remediation.
  • If immediate updating is impossible, assess disabling the plugin until remediation is available.
  • Review payment and order integrity monitoring for unexpected changes.

Validation and detection

  • Confirm the installed plugin slug is woocommerce-gateway-stripe.
  • Record the installed plugin version across production and staging WordPress sites.
  • Flag any installation running version 7.4.0 or older.
  • Verify remediation by confirming the plugin is no longer in the affected version range.
  • Review application logs for suspicious unauthenticated payment or order workflow activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2023-35049 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-35049Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WooCommerceWooCommerce Stripe Payment Gatewaywoocommerce-gateway-stripe, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.