HomeWordPress vulnerabilitiesBuildKit
BuildKit vulnerabilities
BuildKit has 3 known vulnerabilities in this database. The most recent published record is dated 5 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- 300+
- Latest version
- 1.0.29
- Last updated
- 29 Sep 2026
- Most recent
- 5 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Security weakness CVE-2026-97275 | Medium 5.3 | Up to 1.0.28 | Fixed in a later version (latest 1.0.29) | 2 d ago |
| SQL injection CVE-2026-94298 | Medium 6.2 | Before 1.0.29 | Fixed in 1.0.29 | 5 d ago |
| SQL injection CVE-2026-102379 | High 8.5 | Up to 1.0.28 | Fixed in a later version (latest 1.0.29) | 6 d ago |
Read the published descriptions
- CVE-2026-97275, 5 Oct 2026
- Improper Validation of Specified Quantity in Input vulnerability in VillaTheme BuildKit - Product Builder for WooCommerce - Custom PC Builder woo-product-builder allows Input Data Manipulation.This issue affects BuildKit - Product Builder for WooCommerce - Custom PC Builder: from n/a through 1.0.28. CVE record
- CVE-2026-94298, 2 Oct 2026
- The BuildKit WordPress plugin before 1.0.29 does not properly sanitise and escape data submitted by contributor-level users before storing it and later using it in a SQL query, allowing a Contributor to inject SQL that runs against the database once the resulting content is published and viewed by any unauthenticated visitor. CVE record
- CVE-2026-102379, 1 Oct 2026
- Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VillaTheme BuildKit - Product Builder for WooCommerce - Custom PC Builder woo-product-builder allows Blind SQL Injection.This issue affects BuildKit - Product Builder for WooCommerce - Custom PC Builder: from n/a through 1.0.28. CVE record
What to do if you run BuildKit
If you run BuildKit, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new BuildKit vulnerabilities
Free. We email you when a new vulnerability is published for BuildKit, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.