CrowdSecLive Exploit Tracker
Limited ExploitationCVE-2024-0705Public Exploit

Stripe Payment Plugin for WooCommerce - SQLi (CVE-2024-0705)

PublishedJan 19, 2024
First SeenN/A
Last Seen
Reported
CVSS9.8
Webtoffee
WebtoffeeStripe Payment Plugin for WooCommerce
wordpresscmsecommerce

Description

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.

psychologyCrowdSec Analysis

CVE-2024-0705 is a critical SQL injection vulnerability in the Stripe Payment Plugin for WooCommerce, affecting all versions up to and including 3.7.9. This flaw allows unauthenticated attackers to manipulate the 'id' parameter, enabling them to execute arbitrary SQL queries and potentially extract sensitive information from the WordPress database. Exploitation of this vulnerability could lead to data breaches, unauthorized access, or even full compromise of the affected site.

CrowdSec has been tracking this vulnerability and its exploits since 18th of February 2026.

CrowdSec has not observed any significant exploitation activity targeting CVE-2024-0705 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.

Attackers exploit the / endpoint with the wc-api=wt_stripe query parameter by sending crafted JSON payloads where the id field contains SQL injection payloads, allowing unauthenticated execution of arbitrary SQL queries.

lock

Full Intelligence Available

Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.

EventDate
CVE Published2024-01-19
Rule Released2026-02-18

Related Weaknesses

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

arrow_forward

Remediation & Protection

lock to download blocklists, subscribe to firewalls, and access IP intelligence.

External References