Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-0705: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in webtoffee Stripe Payment Plugin for WooCommerce

0
Critical
VulnerabilityCVE-2024-0705cvecve-2024-0705cwe-89
Published: Fri Jan 19 2024 (01/19/2024, 09:31:18 UTC)
Source: CVE Database V5
Vendor/Project: webtoffee
Product: Stripe Payment Plugin for WooCommerce

Description

CVE-2024-0705 is a critical SQL Injection vulnerability in the Stripe Payment Plugin for WooCommerce affecting all versions up to 3. 7. 9. The flaw arises from improper sanitization of the 'id' parameter, allowing unauthenticated attackers to inject malicious SQL queries. This can lead to unauthorized access to sensitive database information, complete compromise of data integrity, and potential disruption of service. The vulnerability requires no authentication or user interaction and has a CVSS score of 9. 8, indicating a severe risk. Although no known exploits are currently reported in the wild, the widespread use of WooCommerce and this plugin makes it a high-value target. Organizations using this plugin should prioritize patching or mitigation to prevent data breaches and operational impact. Countries with significant WooCommerce market share and e-commerce activity are most at risk.

AI-Powered Analysis

AILast updated: 02/26/2026, 11:11:46 UTC

Technical Analysis

CVE-2024-0705 is a critical SQL Injection vulnerability identified in the Stripe Payment Plugin for WooCommerce, a widely used WordPress plugin that facilitates Stripe payment processing. The vulnerability exists due to improper neutralization of special elements in SQL commands (CWE-89), specifically through the 'id' parameter in the plugin's code. Versions up to and including 3.7.9 fail to properly escape or prepare SQL queries involving this parameter, allowing an unauthenticated attacker to append arbitrary SQL code. This can lead to unauthorized extraction of sensitive data from the backend database, including payment information, user data, and other confidential records. The vulnerability is remotely exploitable without any authentication or user interaction, increasing its risk profile. The CVSS v3.1 base score of 9.8 reflects the high impact on confidentiality, integrity, and availability, combined with the ease of exploitation. While no public exploits have been reported yet, the vulnerability's presence in a popular e-commerce plugin makes it a prime target for attackers aiming to compromise online stores and their customers. The lack of a patch link suggests that users must monitor vendor updates closely or implement immediate mitigations to reduce exposure.

Potential Impact

The impact of CVE-2024-0705 on organizations worldwide is substantial. Exploitation can lead to unauthorized disclosure of sensitive customer and payment data, violating privacy regulations such as GDPR and PCI DSS, and resulting in legal and financial penalties. Attackers could manipulate or delete critical database records, undermining data integrity and potentially causing transaction failures or fraudulent activities. The availability of the e-commerce platform could also be disrupted, leading to loss of revenue and customer trust. Given the plugin's widespread adoption among WooCommerce users, many small to medium-sized businesses are at risk, especially those lacking robust security monitoring or timely patch management. The vulnerability's ease of exploitation without authentication increases the likelihood of automated attacks and mass exploitation campaigns. Additionally, compromised stores could serve as launch points for further attacks within organizational networks or supply chains.

Mitigation Recommendations

To mitigate CVE-2024-0705, organizations should immediately upgrade the Stripe Payment Plugin for WooCommerce to a patched version once released by the vendor. Until a patch is available, implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the 'id' parameter. Employ strict input validation and sanitization at the application level, rejecting unexpected or malformed input. Restrict database user permissions to the minimum necessary to limit the impact of a potential injection. Monitor logs for suspicious SQL query patterns or unusual database access. Conduct regular security assessments and penetration testing focused on injection flaws. Additionally, consider isolating the WordPress environment and using database activity monitoring tools to detect and respond to anomalous queries in real time. Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in the future.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-01-18T21:06:45.399Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6de4b7ef31ef0b5903ac

Added to database: 2/25/2026, 9:47:16 PM

Last enriched: 2/26/2026, 11:11:46 AM

Last updated: 2/26/2026, 11:17:42 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats