GHSA-qqf5-x7mj-v43p: budibase: Database Connector SQL Injections in PostgreSQL, MS SQL, and MySQL
Summary This advisory covers three distinct SQL Injection vulnerabilities within Budibase's database connectors (PostgreSQL, Microsoft SQL Server, and MySQL). Because user-controlled schema and table configurations are interpolated directly into raw SQL queries without proper escaping or parameterization during database introspection, an authenticated administrator can break out of string delimiters.
Published Jun 18, 2026
Affected packages
budibase
- Ecosystem
- npm
- Affected
- < 3.39.19
- Fixed in
- 3.39.19
- Check
npm ls budibase
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
This advisory covers three distinct SQL Injection vulnerabilities within Budibase's database connectors (PostgreSQL, Microsoft SQL Server, and MySQL). Because user-controlled schema and table configurations are interpolated directly into raw SQL queries without proper escaping or parameterization during database introspection, an authenticated administrator can break out of string delimiters. This allows for arbitrary DDL/DML execution, database compromise, and potential underlying OS command execution (e.g., via MS SQL xp_cmdshell).
Details
Vulnerability Type & Title
PostgreSQL `SET search_path` SQL Injection
Description & Root Cause
The schema datasource config field is interpolated directly into a raw SQL statement without proper escaping. Double quotes inside the schema name are not escaped, allowing an attacker to break out of the string literal and inject arbitrary SQL.
Vulnerable Code: File: packages/server/src/integrations/postgres.ts, lines 355–358
const search_path = this.config.schema
.split(",")
.map(item => `"${item.trim()}"`) // NO escaping of embedded "
await this.client.query(`SET search_path TO ${search_path.join(",")};`)node-postgres sends this via the simple query protocol, which supports multi-statement execution with semicolons.
Step-by-Step Reproduction
- Edit a PostgreSQL datasource configuration.
- Set the schema field to:
public"; CREATE TABLE pwned AS SELECT usename, passwd FROM pg_shadow; -- - Save or trigger a connection test.
- The query executes as:
SET search_path TO "public"; CREATE TABLE pwned AS SELECT usename, passwd FROM pg_shadow; --; - PostgreSQL executes both statements.
Impact
- Full database compromise. The attacker can read
pg_shadowhashes, callpg_read_file(), or execute any DDL/DML.
---
Vulnerability Type & Title
Microsoft SQL Server Schema Introspection SQL Injection
Description & Root Cause
Three methods used during schema introspection (buildSchema) interpolate user-controlled values directly into SQL strings using single-quote delimiters with no escaping.
Vulnerable Code: File: packages/server/src/integrations/microsoftSqlServer.ts, lines 388–414
getDefinitionSQL(tableName: string, schemaName: string) {
return `select * from INFORMATION_SCHEMA.COLUMNS
where TABLE_NAME='${tableName}' AND TABLE_SCHEMA='${schemaName}'`
}schemaName comes directly from this.config.schema (user config).
Step-by-Step Reproduction
- Edit an MS SQL Server datasource configuration.
- Set the schema field to:
dbo'; EXEC xp_cmdshell('whoami'); -- - Trigger schema introspection (fetch tables).
- The OS command executes on the SQL server if
xp_cmdshellis enabled.
Impact
- Arbitrary SQL execution, potentially leading to OS command execution via
xp_cmdshell.
---
Vulnerability Type & Title
MySQL `multipleStatements: true` + `DESCRIBE` Backtick Injection
Description & Root Cause
The MySQL integration enables multipleStatements: true, allowing semicolon-separated multi-statement execution. When introspecting tables, table names are interpolated into a DESCRIBE query wrapped in backticks, but the backticks are not escaped.
Vulnerable Code: File: packages/server/src/integrations/mysql.ts, lines 172, 305
this.config = { ...config, multipleStatements: true, ... } // line 172
...
{ sql: `DESCRIBE \`${tableName}\`;` } // line 305 — backtick NOT escapedStep-by-Step Reproduction
- An attacker (or malicious database user) creates a table named `
foo; DROP TABLE users; --``. - In Budibase, an admin triggers schema introspection for the database.
- Budibase reads the malicious table name from
INFORMATION_SCHEMA.TABLESand inserts it into theDESCRIBEquery. - The backtick breaks out, and the secondary
DROP TABLEpayload executes.
Impact
- Arbitrary SQL execution triggered during schema discovery. Requires prior database catalog manipulation.
Credited to mhr-isham, Mouhebbenelwafi.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-48128
Budibase: SSRF via User-Controlled queryId in Automation Execute Query Step
medium5.1Jun 12, 2026CVE-2026-46426
Budibase: Unrestricted Upload of File with Dangerous Type
high7.6May 19, 2026CVE-2026-45718
Budibase: Row Action Trigger Bypasses View Row Filter Security Boundary Allowing Action on Out-of-Scope Rows
medium5.4May 18, 2026CVE-2026-45061
Budibase vulnerable to SSRF via trivial `.tar.gz` substring bypass in Plugin URL upload (`/api/plugin`)
high7.7May 11, 2026CVE-2026-33226
Budibase Unrestricted Server-Side Request Forgery (SSRF) via REST Datasource Query Preview
high8.7No fixMar 18, 2026CVE-2026-27702
Budibase: Remote Code Execution via Unsafe eval() in View Filter Map Function (Budibase Cloud)
critical9.9Feb 25, 2026
