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-97275 Overview
CVE-2026-97275 is an input validation vulnerability in the VillaTheme BuildKit – Product Builder for WooCommerce – Custom PC Builder plugin (woo-product-builder). The flaw stems from improper validation of specified quantity in input, allowing unauthenticated attackers to manipulate input data sent to the plugin. The issue affects all plugin versions from n/a through 1.0.28. Classified under CWE-1284, the vulnerability exposes WooCommerce storefronts running custom PC builder workflows to integrity-related manipulation over the network without privileges or user interaction.
Critical Impact
Unauthenticated remote attackers can submit malformed quantity values to WooCommerce product builder endpoints, resulting in integrity-impacting data manipulation on affected stores.
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-05 - CVE-2026-97275 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-97275
Vulnerability Analysis
The BuildKit plugin lets WooCommerce shoppers assemble custom products such as PC builds by submitting component selections and quantities. The affected code paths do not properly validate the quantity values supplied by the client. An attacker can submit values that fall outside the expected bounds, including negative numbers, zero, extremely large integers, or non-integer types that the application later treats as valid.
Because the plugin trusts attacker-controlled quantities during cart or build operations, downstream calculations for pricing, inventory, and order totals can be subverted. The impact is scoped to integrity (I:L) with no confidentiality or availability impact per the CVSS vector.
Root Cause
The root cause is categorized as CWE-1284: Improper Validation of Specified Quantity in Input. The plugin accepts user-supplied quantity parameters without enforcing type, range, or business-logic constraints before passing them to WooCommerce cart or order processing routines. This allows input data manipulation that bypasses expected purchase constraints.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker sends a crafted HTTP request to the WooCommerce endpoint exposed by the woo-product-builder plugin, supplying manipulated quantity fields in the product builder submission payload. The server accepts the malformed values and processes the cart or build request, resulting in integrity impact to orders, pricing, or inventory records.
No verified public proof-of-concept code is available. See the Patchstack WooCommerce Plugin Vulnerability advisory for the vendor-coordinated disclosure.
Detection Methods for CVE-2026-97275
Indicators of Compromise
- Orders containing line items with zero, negative, or unusually large quantity values originating from the custom PC builder flow.
- WooCommerce order totals that do not match the sum of configured components or exhibit unexpected discounts.
- Unusual spikes in requests to woo-product-builder AJAX or REST endpoints from a single source IP.
Detection Strategies
- Inspect WooCommerce order metadata and build logs for product builder submissions where quantity fields deviate from allowed ranges.
- Enable web application firewall rules that assert strict integer typing and positive-range validation on quantity parameters sent to WordPress endpoints.
- Correlate anomalous order patterns with HTTP access logs targeting plugin endpoints under /wp-admin/admin-ajax.php or /wp-json/.
Monitoring Recommendations
- Monitor WordPress and WooCommerce logs for repeated failed or malformed cart submissions tied to the plugin.
- Alert on order fulfillment anomalies such as negative inventory decrements or zero-priced line items.
- Track plugin version inventory across WordPress estates to identify hosts still running woo-product-builder version 1.0.28 or earlier.
How to Mitigate CVE-2026-97275
Immediate Actions Required
- Identify all WordPress sites running the BuildKit – Product Builder for WooCommerce plugin and record the installed version.
- Upgrade woo-product-builder to a release above 1.0.28 as soon as a patched version is published by VillaTheme.
- Audit recent orders generated through the custom PC builder for suspicious quantity or pricing anomalies.
Patch Information
At the time of publication, the affected version range is n/a through 1.0.28. Consult the Patchstack advisory and the VillaTheme plugin changelog for the fixed version and apply the update through the WordPress plugin manager.
Workarounds
- Temporarily deactivate the woo-product-builder plugin on production stores until a patched version is applied.
- Deploy a web application firewall rule that rejects requests to plugin endpoints when quantity parameters are non-integer, zero, negative, or above a documented maximum.
- Restrict access to the product builder endpoints by IP or rate limit submissions to reduce automated manipulation.
# Example WAF rule concept (ModSecurity-style) to drop malformed quantity values
SecRule ARGS_NAMES "@rx (?i)quantity" \
"chain,deny,status:400,id:1029727501,msg:'Block malformed quantity for woo-product-builder'"
SecRule ARGS:/quantity/ "!@rx ^[1-9][0-9]{0,3}$" "t:none"
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

