Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

Quick assessment

Affected
budibase server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Budibase 3.45.0 版本之前, 组件在 中构建 MySQL 和 MSSQL 的列重命名 DDL(数据定义语言)语句时,存在直接插值漏洞。具体而言,标识符被直接插入到原始查询字符串中(MySQL 使用反引号包裹,MSSQL 使用单引号包装的 字面量),而未能应用项目内置的 / 安全辅助函数进行正确转义。 具备连接 MySQL 或 MSSQL 数据源 DDL 权限的攻击者,可以创建一个列名中包含特殊字符的列:对于 MySQL,列名可包含反引号及额外 SQL 代码;对于 MSSQL,列名可包含单引号及额外

CVSS 8.0 · High EPSS 0.21% · P10
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-100683

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Budibase before 3.45.0 SQL Injection via column-rename DDL
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
SQL命令中使用的特殊元素转义处理不恰当(SQL注入)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
budibase server 0 ~ 3.45.0 -

II. Public POCs for CVE-2026-100683

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-100683

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-100683 (1)

Other References for CVE-2026-100683 (1)

Same Patch Batch · budibase · 2026-09-26 · 9 CVEs total

CVE-2026-100682 8.8 HIGH Budibase Server before 3.45.0 Arbitrary File Write via ZIP Symlink
CVE-2026-100686 8.1 HIGH Budibase before 3.45.0 Cross-Workspace Privilege Escalation via POST /api/global/groups/:g
CVE-2026-100684 8.1 HIGH Budibase Server 3.41.0 before 3.45.0 Authentication Bypass via OIDC
CVE-2026-100680 8.1 HIGH Budibase before 3.45.0 Arbitrary Local File Read via OpenAPI Import
CVE-2026-100685 7.7 HIGH Budibase before 3.45.0 Information Disclosure via Chat Links
CVE-2026-100688 6.5 MEDIUM Budibase server before 3.45.0 Cross-Tenant Information Disclosure
CVE-2026-100687 5.5 MEDIUM Budibase Server before 3.45.0 Credential Exposure via External Table Broadcast
CVE-2026-100681 5.4 MEDIUM Budibase before 3.45.0 SSRF and OAuth Token Exfiltration via Teams Webhook

IV. Related Vulnerabilities

V. Comments for CVE-2026-100683

No comments yet


Leave a comment