Security readout for executives and security teams
Plain-English summary
Budibase versions before 3.40.0 can allow hostile input to alter MySQL queries and run additional database statements. Successful exploitation could expose, modify, or destroy database information, potentially causing complete database compromise. The published CVSS score is 9.6, making this an urgent issue for organizations using the affected integration.
Executive priority
Treat this as an immediate remediation priority for affected Budibase deployments. Determine within the shortest practical timeframe whether versions below 3.40.0 use MySQL, then upgrade. Because successful exploitation could compromise the entire database, potentially affected systems should also receive focused log review and incident-response triage.
Technical view
The MySQL integration enabled multipleStatements, allowing more than one SQL statement per query. Combined with insufficiently controlled user input, this creates CWE-89 SQL injection. The CVSS vector indicates network reachability, low complexity, no privileges, required user interaction, changed scope, and high confidentiality, integrity, and availability impact. Version 3.40.0 contains the fix.
Likely exposure
Exposure applies to Budibase versions earlier than 3.40.0 using the MySQL integration. Risk is greatest where untrusted users can reach input fields connected to vulnerable database queries. The supplied sources do not identify every prerequisite, affected application design, or whether Internet exposure is required.
Exploitation context
The supplied bundle does not report known active exploitation, and the CVE is not identified as KEV. That does not establish that exploitation has never occurred. The vulnerability is remotely reachable according to its CVSS vector, requires user interaction, needs no attacker privileges, and could result in complete database compromise.
Researcher notes
The central risk is stacked SQL execution enabled by multipleStatements: true. The public description attributes complete database compromise to injected commands through user input fields. It does not provide enough evidence to characterize exact vulnerable endpoints, payload constraints, observed attacks, or deployment-specific reachability. Validate exposure without attempting destructive testing.
Mitigation direction
- Upgrade affected Budibase deployments to version 3.40.0 or later.
- Prioritize deployments using the MySQL integration and accepting untrusted input.
- Restrict access to affected applications until upgrading where operationally feasible.
- Consult the Budibase advisory and release notes for vendor-supported remediation details.
- Initiate incident response and protect database credentials if compromise is suspected.
Validation and detection
- Inventory Budibase deployments and record their exact versions.
- Identify deployments using Budibase's MySQL integration.
- Confirm each relevant deployment runs version 3.40.0 or later.
- Review database logs for unexpected or additional SQL statements.
- Check affected applications for untrusted input reaching database-backed fields.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73300 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Budibase/budibase/security/advisories/GHSA-q6x4-v3qx-85qwCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Budibase/budibase/releases/tag/3.40.0CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.