WooCommerce Stripe Payment Gateway <= 7.6.1 - Insecure Direct Object Reference via update_payment_intent_ajax
Strategic Overview
- Status
- Patched in 7.6.2
- Affected Plugin
- WooCommerce Stripe Payment Gateway
- Affected Version
<= 7.6.1- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2023-51502
At a glance
CVE-2023-51502 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WooCommerce Stripe Payment Gateway WordPress plugin, affecting versions <= 7.6.1. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.6.2; sites on affected versions should update now. Disclosed December 2023, reported by Rafie Muhammad.
Vulnerability Overview
The WooCommerce Stripe Payment Gateway plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.6.1 via the update_payment_intent_ajax due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to make updates to payments that don't belong to their orders.
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.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in WooCommerce Stripe Payment Gateway <= 7.6.1 takes a caller who can reach the endpoint. 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 7.6.2: builds <= 7.6.1 are affected, anything from 7.6.2 onward is not.
Remediation
Update to version 7.6.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WooCommerce Stripe Payment Gateway 7.6.2 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