SQL Injection in Budibase (CVE-2026-100683)
Summary
SQL injection in Budibase (CVE-2026-100683). Successful exploitation can lead to full system takeover. Exploitable via POST /api/tables. Mitigation: upgrade to 3.45.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-100683 has been found in Budibase.
Attackers can target a specific entry point like POST /api/tables over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade Budibase to 3.45.0 or later.
If unsure, ask your IT team or search "Budibase CVE-2026-100683" on the vendor's site.
CVE-2026-100683 (Budibase) — CWE-89 / CVSS v3 8.0
Attack vector: remote (network-reachable)
Attack surface: POST /api/tables
Patched: 3.45.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in Budibase. Attackers reach the vulnerable code path via POST /api/tables.
Check the vendor advisory for the affected versions of Budibase. Attack surface: POST /api/tables.
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.
Update to 3.45.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/tables requests with malformed payloads or SQL meta-characters. Run grep -r 'Budibase' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Budibase' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Budibaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/tables' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/tablesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Budibase to 3.45.0ステージング環境で 3.45.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/tables on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com