Quick answers
- Is CVE-2026-100683 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100683 being exploited in the wild.
- How severe is CVE-2026-100683?
- High severity, with a CVSS score of 8, published 26 September 2026.
- Which products and versions are affected?
- Budibase Server before 3.45.0.
- Is there a fix for CVE-2026-100683?
- A patch was published on 2026-09-26: Fixed in version 3.45.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100683 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100683?
- Check whether you run Budibase Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Second-order SQL identifier injection in sqlTable.ts where MySQL and MSSQL column-rename operations interpolate identifiers directly into raw query strings without applying quoteMySqlIdentifier/quoteSqlServerIdentifier helpers. An attacker with DDL rights creates a column name containing a backtick (MySQL) or single quote (MSSQL) followed by stacked SQL; when a builder renames that column via POST /api/tables, the quote character breaks the identifier context and executes the injected SQL as Budibase's datasource user on the external database. MySQL multipleStatements: true enables full stacked query execution.
Affected products
- Budibase @budibase/server before 3.45.0
Timeline
- 2026-09-26: disclosed
- 2026-09-26: patched: Fixed in version 3.45.0