Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102379 Overview
CVE-2026-102379 is a blind SQL injection vulnerability in the VillaTheme BuildKit – Product Builder for WooCommerce – Custom PC Builder plugin (woo-product-builder) for WordPress. The flaw affects all versions up to and including 1.0.28. An authenticated attacker with low privileges can inject arbitrary SQL into database queries over the network. The vulnerability is classified under CWE-89, Improper Neutralization of Special Elements used in an SQL Command.
Critical Impact
Low-privileged attackers can extract sensitive WooCommerce store data, including customer records, order details, and credential hashes, through blind SQL injection with a changed scope impacting the entire database.
Affected Products
- VillaTheme BuildKit – Product Builder for WooCommerce – Custom PC Builder
- Plugin slug: woo-product-builder
- Versions from n/a through 1.0.28
Discovery Timeline
- 2026-10-01 - CVE-2026-102379 published to NVD
- 2026-10-01 - Last updated in NVD database
Technical Details for CVE-2026-102379
Vulnerability Analysis
The BuildKit plugin provides a custom product builder interface for WooCommerce stores. One or more plugin endpoints accept user-controlled input that reaches a SQL query without proper sanitization or parameterization. This allows an authenticated user to influence query logic directly.
The injection is blind, meaning the application does not return query results in HTTP responses. Attackers infer data by observing differential behavior, timing, or boolean conditions. Blind SQL injection remains fully exploitable through automated tooling such as sqlmap.
The CVSS vector indicates a scope change, meaning exploitation affects resources beyond the vulnerable plugin itself. In WordPress, this reflects access to the broader site database, including core tables like wp_users and wp_usermeta.
Root Cause
The root cause is improper neutralization of special characters in SQL statements. The plugin concatenates user-supplied input into SQL queries without using WordPress prepared statement APIs such as $wpdb->prepare(). Any single-quote, comment delimiter, or SQL keyword passed through the vulnerable parameter is interpreted as query syntax.
Attack Vector
Exploitation requires network access and authenticated low-privilege credentials, such as a Subscriber or Customer account on the WooCommerce store. WooCommerce installations commonly permit open customer registration, lowering the barrier to obtaining the required privilege level. The attacker submits crafted payloads to the vulnerable plugin endpoint and uses boolean-based or time-based inference techniques to enumerate database contents. See the Patchstack SQL Injection Advisory for additional technical context.
Detection Methods for CVE-2026-102379
Indicators of Compromise
- Unusual SQL syntax in HTTP request parameters sent to /wp-admin/admin-ajax.php or plugin-specific endpoints under /wp-content/plugins/woo-product-builder/.
- Repeated requests from authenticated low-privilege accounts containing SQL keywords such as SLEEP, BENCHMARK, UNION SELECT, AND 1=1, or OR 1=2.
- Spikes in database query latency correlated with specific user sessions, consistent with time-based blind injection.
- Web server access logs showing high request volume to BuildKit AJAX actions from a single authenticated user.
Detection Strategies
- Deploy a Web Application Firewall (WAF) with SQL injection signatures tuned for WordPress AJAX actions.
- Enable WordPress query logging or MySQL general query log review to identify malformed statements targeting plugin tables.
- Correlate authentication events with suspicious parameter payloads to attribute activity to specific accounts.
Monitoring Recommendations
- Monitor for new or unexpected low-privilege account registrations followed by immediate requests to plugin endpoints.
- Alert on repeated HTTP 500 errors from BuildKit endpoints, which may indicate injection probing.
- Track outbound data volume from the WordPress host to detect staged database exfiltration.
How to Mitigate CVE-2026-102379
Immediate Actions Required
- Identify all WordPress sites running the BuildKit – Product Builder plugin at version 1.0.28 or earlier.
- Disable the woo-product-builder plugin until a patched version is installed if the plugin is not business-critical.
- Audit user accounts and remove any suspicious low-privilege registrations created recently.
- Rotate WordPress administrator credentials and any API keys stored in the database if exploitation is suspected.
Patch Information
At time of publication, no fixed version is referenced in the NVD entry. Monitor the Patchstack SQL Injection Advisory and the VillaTheme vendor channel for an updated release of woo-product-builder that addresses CVE-2026-102379.
Workarounds
- Restrict customer registration to trusted email domains or require manual approval for new accounts.
- Deploy a virtual patch through a WAF such as Patchstack, Wordfence, or ModSecurity to block injection payloads targeting the plugin.
- Enforce the principle of least privilege by removing unnecessary user roles and disabling accounts that do not require store access.
# Example: disable the vulnerable plugin via WP-CLI
wp plugin deactivate woo-product-builder
wp plugin status woo-product-builder
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

