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

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

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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 available:** No
- **Published:** 26 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-8mm2-5qwq-x6xp, GHSA-ppj8-hmx2-m546

## 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 (Improper Neutralization of Special Elements used in an SQL Command)

## 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.

## Is CVE-2026-100683 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100683 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100683 exists.

Affected product: budibase server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100683/ (Markdown: https://insights.sbomify.com/CVE-2026-100683/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100683
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100683
- OSV: https://osv.dev/vulnerability/CVE-2026-100683

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100683/
Summaries are generated and may contain mistakes; the official description above is the record.