Skip to main content
VulnerabilityPublished

CVE-2026-94298: BuildKit (WordPress plugin) · SQL Injection

Affects BuildKit (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 1.0.29 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.29
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade BuildKit (WordPress plugin) to 1.0.29.

Affected software

ProductAffectedFixed in
BuildKitAffected
  • <1.0.29
Fixed in
  • 1.0.29

AI-suggested

Upgrade the BuildKit plugin to version 1.0.29 or later, where this vulnerability is fixed. No other mitigation guidance is provided. Since this is a plugin vulnerability, patching to the fixed version is the recommended action.

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.

References

Community reviews

Loading reviews…