PatchSiren cyber security CVE debrief
CVE-2026-100683 budibase CVE debrief
Budibase server versions before 3.45.0 are vulnerable to SQL injection attacks via column-rename DDL operations. The vulnerability arises from the direct interpolation of identifiers into raw query strings without proper quoting, allowing an attacker with DDL rights on a connected MySQL or MSSQL datasource to inject malicious SQL. This can lead to arbitrary reads, writes, or destructive operations on the connected database outside of Budibase's row/table permission model.
- Vendor
- budibase
- Product
- server
- CVSS
- HIGH 8.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-26
- Original CVE updated
- 2026-10-08
- Advisory published
- 2026-09-26
- Advisory updated
- 2026-10-08
Who should care
Budibase server administrators and users with DDL rights on connected MySQL or MSSQL datasources should assess their exposure and prioritize updating to version 3.45.0 or later, considering potential impacts on database permissions, integrity, and user permissions.
Why it matters
Budibase server versions before 3.45.0 are vulnerable to SQL injection attacks via column-rename DDL operations, potentially allowing for exploitation of database permissions and arbitrary reads, writes, or destructive operations.
- Potential for arbitrary database reads and writes
- Possible exploitation of database permissions
- Risk of destructive operations on connected databases
- Need for verification of database integrity and user permissions
Technical summary
The Budibase server is vulnerable to SQL injection attacks via column-rename DDL operations. The vulnerability exists in versions before 3.45.0 and is caused by the direct interpolation of identifiers into raw query strings without proper quoting. An attacker with DDL rights on a connected MySQL or MSSQL datasource can inject malicious SQL, potentially leading to arbitrary reads, writes, or destructive operations on the connected database.
Defensive priority
High priority should be given to updating Budibase server to version 3.45.0 or later, as the vulnerability allows for potential exploitation of database permissions.
Recommended defensive actions
- Update Budibase server to version 3.45.0 or later
- Review database permissions and restrict DDL rights where possible
- Monitor database activity for suspicious queries
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and source item provide details on the vulnerability, including the affected versions and the fixed version. However, there is limited information on potential exploitation or victim impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-100683 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-100683
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-100683 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-100683
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Budibase before 3.45.0 SQL Injection via column-rename DDL
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/100xxx/CVE-2026-100683.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/Budibase/budibase/security/advisories/GHSA-ppj8-hmx2-m546
Supplemental source - vendor-advisory
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/budibase-before-3.45.0-sql-injection-via-column-rename-ddl
Supplemental source - third-party-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.