CVE-2026-100683 Budibase before 3.45.0 SQL Injection via column-rename DDL

High 8.9 Published Updated

Attacker with DDL rights can inject SQL via column rename, bypassing permissions to read or modify database data.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-100683?

CVE-2026-100683 is a high-severity SQL injection vulnerability in budibase server, published on 26 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Budibase (@budibase/server) before 3.45.0 builds MySQL and MSSQL column-rename DDL in packages/backend-core/src/sql/sqlTable.ts by interpolating identifiers directly into a raw query string (backtick-quoted for MySQL, a single-quoted sp_rename literal for MSSQL) without applying the project's quoteMySqlIdentifier / quoteSqlServerIdentifier helpers. An attacker with DDL rights on a connected MySQL/MSSQL datasource can create a column whose name contains a backtick (MySQL) or single quote (MSSQL) plus additional SQL; Budibase's schema introspection stores the name verbatim, and when a Budibase builder later renames that column through the UI (POST /api/tables with _rename.old), the embedded quote character terminates the identifier and the injected SQL is executed. Because the MySQL connection is opened with multipleStatements: true, stacked statements run as Budibase's datasource user, allowing arbitrary reads, writes, or destructive operations on the connected database outside Budibase's row/table permission model. Fixed in 3.45.0.

Weakness: CWE-89

Which versions are affected by CVE-2026-100683?

How do I fix CVE-2026-100683?

No fix has been published for CVE-2026-100683 yet. Limit exposure of the affected software until one is available.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-100683 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100683 exists.

Sources

Also known as GHSA-8mm2-5qwq-x6xp, GHSA-ppj8-hmx2-m546.

Is CVE-2026-100683 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free