CVE-2026-100683
Budibase (@budibase/server) before 3.45.0 builds MySQL and MSSQL column-rename DDL in…
- Risk score
- 50/100
- CVSS
- 8.0 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 26 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 / qu…
- Affected
- See advisory
- Fix
- Upgrade the product to 3.45.0 or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.0 high
References
Original 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.
Last activity 26 Sep 2026. Patch Forecast updates every hour.