WooCommerce Stripe Payment Gateway <= 7.4.0 - Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 5.5.1
- Affected Plugin
- WooCommerce Stripe Payment Gateway
- Affected Version
5.5.0 – 7.4.0 · 21 branches- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-34000
At a glance
CVE-2023-34000 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WooCommerce Stripe Payment Gateway WordPress plugin, affecting versions 5.5.0 – 7.4.0 · 21 branches. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 5.5.1; sites on affected versions should update now. Disclosed June 2023, reported by Rafie Muhammad.
Vulnerability Overview
The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 7.4.0. This is due to insufficient validation in the payment_fields() and javascript_params () functions that do not properly validate order ownership. This makes it possible for unauthenticated attackers to retrieve potentially sensitive data for orders other than their own.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
WooCommerce Stripe Payment Gateway 5.5.0 – 7.4.0 · 21 branches carries this weakness at payment_fields(), and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WooCommerce Stripe Payment Gateway the fix is 5.5.1: builds 5.5.0 – 7.4.0 · 21 branches are affected, anything from 5.5.1 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 5.5.1, 5.6.3, 5.7.1, 5.8.2, 5.9.1, 6.0.1, 6.1.1, 6.2.1, 6.3.1, 6.4.4, 6.5.2, 6.6.1, 6.7.1, 6.8.1, 6.9.1, 7.0.3, 7.1.1, 7.2.1, 7.3.1, 7.4.1
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WooCommerce Stripe Payment Gateway 5.5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WooCommerce Stripe Payment Gateway
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C