CVE-2026-94298

BuildKit < 1.0.29 - Contributor+ Stored SQLi via list_content Parameter

Published Oct 2, 2026 CVSS 3.1 · 6.2 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The BuildKit WordPress plugin before 1.0.29 fails to sanitize and escape data submitted by contributor‑level users. The list_content parameter is stored directly and later incorporated into a database query without proper escaping. A malicious contributor can inject SQL that executes when the stored content is published and viewed by any visitor, potentially exposing, modifying, or deleting data in the site database.

Affected Systems

Any WordPress installation using the BuildKit plugin version earlier than 1.0.29 is affected. The vulnerability exists in the plugin code managing the list_content field and requires that a user has the Contributor role.

Risk and Exploitability

Because the flaw is a stored SQL injection, exploitation requires the attacker to have contributor privileges, which is a relatively low‑privilege level commonly granted for content authors. Once injected, the associated SQL runs with the privileges of the web application’s database user. While no publicly reported exploit is referenced in the CVE description, it cannot be ruled out that attackers may target this flaw. The EPSS score is below 1%, indicating a very low but non‑zero perceived exploitation probability, and the KEV designation is absent, suggesting no known exploitation in the CISA catalog. The CVSS score of 6.2 reflects medium severity, but the potential impact remains significant, especially in environments with sensitive data, because unauthenticated visitors can trigger the injected SQL when viewing the published content.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update BuildKit to version 1.0.29 or later
  • Disable or remove the BuildKit plugin if an update is not feasible
  • Restrict the Contributor role or remove contributor privileges from untrusted users
  • Apply additional input validation or use parameterized queries to ensure list_content is safely handled

Generated by OpenCVE AI on October 2, 2026 at 14:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions buildkit
Vendors & Products Wordpress-extensions
Wordpress-extensions buildkit
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-89
Type Values Removed Values Added
Description 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.
Title BuildKit < 1.0.29 - Contributor+ Stored SQLi via list_content Parameter
References
Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 2, 2026, 10:54 AM
Reserved
Sep 21, 2026, 9:44 AM
Status
Deferred
Published
Oct 2, 2026, 6:16 AM
Modified
Oct 2, 2026, 6:00 PM