Budibase: MySQL DESCRIBE Backtick Injection via multipleStatements in Database Connector

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-73408: 0.45% estimated exploitation activity in the next 30 days; percentile 39.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary This is a related but independently fixable vulnerability to GHSA-qqf5-x7mj-v43p (PostgreSQL SQL injection), reported in the same original disclosure and split per GitHub CNA guidance (rule 4.2.11) since it affects a separate integration, has a distinct attack precondition, and requires a separate patch. The MySQL integration enables multipleStatements: true on the connection, permitting semicolon-separated multi-statement execution. During table introspection, table names retrieved from INFORMATIONSCHEMA.TABLES are interpolated into a DESCRIBE query wrapped in backticks, but embedded backticks in the table name are never escaped — allowing a malicious table name to break out and inject a second, attacker-controlled statement. Details Vulnerable Code: File: packages/server/src/integrations/mysql.ts, lines 172, 305 Because multipleStatements is enabled, any statement appended after the backtick break-out executes as a second query in the same round trip. Step-by-Step…

Published by the source

24 Jul 2026, 21:26 UTC

Last modified by the source

14 Aug 2026, 04:12 UTC

Source last checked

26 Oct 2026, 12:58 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2xgg-r2wc-c5r2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2xgg-r2wc-c5r2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73408

Advisory: Budibase: MySQL DESCRIBE Backtick Injection via multipleStatements in Database Connector
IDs: CVE-2026-73408, GHSA-2xgg-r2wc-c5r2
Record: https://patchnext.com/advisories/cve-2026-73408 (revision 2, source checked 26 Oct 2026, 12:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.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://osv.dev/vulnerability/GHSA-2xgg-r2wc-c5r2 (OSV record GHSA-2xgg-r2wc-c5r2 lists affected ranges: npm @budibase/server >=0 <=3.38.1)
- Verified: https://github.com/advisories/GHSA-2xgg-r2wc-c5r2 (GitHub-reviewed advisory GHSA-2xgg-r2wc-c5r2 lists affected ranges: npm @budibase/server >=0 <=3.38.1)

Commands are suggestions: review each one before running it.