CVE-2024-7854: The Woo Inquiry plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 0.1 due to insufficient escaping on the user supplied…

PriorityP270critical9.8CVSS 3.1

AVNACLPRNUINSUCHIHAH

EXPLOIT

EPSS

4.32%

90.0th percentile

The Woo Inquiry plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 0.1 due to insufficient escaping on the user supplied parameter 'dbid' 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.

Affected

2 ranges

Vendor	Product	Version range	Fixed in
sjhoo	woo_inquiry	<= 0.1	—
sjhoo	woo_inquiry	—	—

Detection & IOCsextracted from sources · hover to see the quote

otherdbid↗

→Monitor for unauthenticated HTTP requests to WordPress sites with the Woo Inquiry plugin (versions <= 0.1) containing SQL injection payloads in the 'dbid' parameter — look for appended SQL syntax such as UNION SELECT, stacked queries, or boolean/time-based blind injection patterns in the 'dbid' field. ↗
→The Nuclei template targets responses with HTTP 200 status and content-type containing 'text/html'; detections should focus on successful SQL injection responses (status 200, text/html) from the Woo Inquiry plugin endpoint.
→The attack is exploitable by unauthenticated users — no session or authentication token is required. Prioritize alerting on 'dbid' parameter manipulation from unauthenticated sessions. ↗

·All versions up to and including 0.1 of the Woo Inquiry plugin for WordPress are vulnerable. Ensure version checks in detection rules cap at version 0.1. ↗

CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.