Budibase: SQL Injection via multipleStatements: true
CVE-2026-73300GHSA-q6x4-v3qx-85qw
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @budibase/server
- Affected
- <= 3.38.1
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q6x4-v3qx-85qw lists affected ranges: npm @budibase/server >=0 <=3.38.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-q6x4-v3qx-85qw lists affected ranges: npm @budibase/server >=0 <=3.38.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- EPSS
- CVE-2026-73300: 0.56% estimated exploitation activity in the next 30 days; percentile 46.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 Proof of Concept Exploit 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 Workarounds 1. Temporarily disable MySQL integration 2. Implement web application firewall (WAF) 3. Restrict database user privileges
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-q6x4-v3qx-85qw
- Revision 2 · amended ·
Amended from osv record GHSA-q6x4-v3qx-85qw
- Revision 1 · created ·
Published from ghsa record GHSA-q6x4-v3qx-85qw
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-73300 Advisory: Budibase: SQL Injection via `multipleStatements: true` IDs: CVE-2026-73300, GHSA-q6x4-v3qx-85qw Record: https://patchnext.com/advisories/cve-2026-73300 (revision 3, source checked 26 Oct 2026, 13:01 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @budibase/server: affected <= 3.38.1 ## Suggested inspection (read-only) - `npm ls @budibase/server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @budibase/server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-q6x4-v3qx-85qw (GitHub-reviewed advisory GHSA-q6x4-v3qx-85qw lists affected ranges: npm @budibase/server >=0 <=3.38.1) - Verified: https://osv.dev/vulnerability/GHSA-q6x4-v3qx-85qw (OSV record GHSA-q6x4-v3qx-85qw lists affected ranges: npm @budibase/server >=0 <=3.38.1) Commands are suggestions: review each one before running it.
Loading voting…