Stripe Payment Plugin for WooCommerce <= 3.7.9 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in 3.8.0
- Affected Plugin
- Payment Gateway of Stripe for WooCommerce
- Affected Version
<= 3.7.9- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-0705
At a glance
CVE-2024-0705 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Payment Gateway of Stripe for WooCommerce WordPress plugin, affecting versions <= 3.7.9. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.8.0; sites on affected versions should update now. Disclosed January 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Stripe Payment Plugin for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 3.7.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Payment Gateway of Stripe for WooCommerce <= 3.7.9 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Payment Gateway of Stripe for WooCommerce the fix is 3.8.0: builds <= 3.7.9 are affected, anything from 3.8.0 onward is not.
Remediation
Update to version 3.8.0, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Payment Gateway of Stripe for WooCommerce 3.8.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Payment Gateway of Stripe for WooCommerce
- 9.8CVE-2023-3162: Stripe Payment for WooCommerce Authentication Bypass
CVE-2023-3162 - 6.1Stripe Payment Plugin for WooCommerce <= 3.5.9 Reflected XSS
- 5.3CVE-2026-45217: Payment Gateway of Stripe… Missing Authorization
CVE-2026-45217 - 5.3CVE-2023-4040: Stripe Payment… Arbitrary Order Status Modification
CVE-2023-4040
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C