GHSA-q6x4-v3qx-85qw
CRITICALBudibase: SQL Injection via `multipleStatements: true`
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@budibase/servernpmDescription
Summary
A critical SQL injection vulnerability was discovered in Budibase's MySQL integration that allows remote attackers to execute arbitrary SQL commands.
Details
Vulnerability Type
SQL Injection
Description
The MySQL integration component in Budibase is configured with multipleStatements: true, enabling execution of multiple SQL statements in a single query. Attackers can inject malicious SQL commands through user input fields, leading to complete database compromise.
Location
// File: packages/server/src/integrations/mysql.ts
// Line: 173
this.config = {
...config,
typeCast: defaultTypeCasting,
multipleStatements: true, // VULNERABLE
timezone: "Z",
}
Proof of Concept
Exploit
const mysql = require('mysql2');
// Budibase vulnerable configuration
const connection = mysql.createConnection({
host: 'localhost',
user: 'root',
password: 'password',
multipleStatements: true, // Vulnerable setting
timezone: "Z"
});
// Attack: Data destruction
connection.query(
`SELECT * FROM users WHERE id = 1; DROP TABLE sensitive_data; --`,
(err, results) => {
if (!err) console.log("Table dropped successfully");
}
);
Impact
- Data Destruction: Execute DROP TABLE, DELETE commands
- Data Theft: Exfiltrate data via SELECT INTO OUTFILE
- Privilege Escalation: Grant database admin privileges
- Denial of Service: Disrupt service operations
- Complete Database Compromise: Full control over database
Remediation
Patch
--- a/packages/server/src/integrations/mysql.ts
+++ b/packages/server/src/integrations/mysql.ts
@@ -170,7 +170,7 @@ class MySQLIntegration extends Sql implements DatasourcePlus {
this.config = {
...config,
typeCast: defaultTypeCasting,
- multipleStatements: true,
+ multipleStatements: false,
timezone: "Z",
}
}
Workarounds
- Temporarily disable MySQL integration
- Implement web application firewall (WAF)
- Restrict database user privileges
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @budibase/server | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @budibase/server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of @budibase/server has shipped for GHSA-q6x4-v3qx-85qw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q6x4-v3qx-85qw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-q6x4-v3qx-85qw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-q6x4-v3qx-85qw in your dependencies?
O3 detects GHSA-q6x4-v3qx-85qw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.