External risk intelligence

Budibase MySQL Integration SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-73300

Budibase is a low-code platform designed for building web applications. These applications are commonly deployed as internet-facing services or business-critical web portals, making the underlying database integration components frequently reachable via web-based user input.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in the Budibase open-source low-code platform, specifically within its MySQL integration. The flaw allows attackers to execute multiple SQL commands, potentially leading to complete database compromise by injecting malicious code through user input. The main concern is confirming relevance and exposure to this technology.

  • Malicious SQL commands can compromise databases.
  • Low-code platforms are often internet-facing.
  • Confirm relevance and exposure of Budibase.

Attack Path

How an attacker could exploit the issue

Attackers can leverage an exposed MySQL integration within Budibase, a low-code platform, to execute arbitrary SQL commands. By injecting malicious SQL through user-controlled input fields in applications built with Budibase, an attacker can gain complete control over the associated database. This vulnerability could lead to data theft, manipulation, or deletion.

  • No privileges required for access.
  • Injecting SQL via user input fields.
  • Complete database compromise.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, the MySQL integration component in Budibase could allow attackers to execute multiple SQL statements, potentially leading to complete compromise of the associated database. This could occur when user input fields within applications built on Budibase are not properly sanitized, allowing for the injection of malicious SQL commands.

  • Database contents at risk.
  • Malicious SQL commands injected via input.
  • Complete database compromise may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

Determining ownership for this critical vulnerability in Budibase's MySQL integration requires identifying which team manages the deployed Budibase instances and their associated databases. The first practical step is to locate all Budibase deployments, assess their exposure and business criticality, pinpoint the exact owner for each instance, and then develop a prioritized remediation plan.

  • Application owners should manage the issue.
  • Verify Budibase instances and their reachability.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Budibase?

Budibase is an open-source low-code platform designed to help developers and business users quickly build internal tools, forms, and web applications. It simplifies the connection to various data sources, including MySQL, allowing these applications to serve as functional portals that interact directly with backend databases.

What does CVE-2026-73300 mean?

This CVE identifies a SQL injection vulnerability, classified as CWE-89. It occurs because the MySQL integration component is configured to allow multiple SQL statements in a single query. An attacker can exploit this by entering malicious SQL commands into input fields, tricking the application into executing unauthorized database operations.

How do attackers trigger this vulnerability?

Attackers trigger this by submitting crafted input into vulnerable fields within a Budibase application. Simply accessing the application does not trigger the bug; the platform must actively process user-provided data through its MySQL integration. If an input field does not interact with the backend database, it is not a vector for this specific injection flaw.

Is my Budibase instance at risk?

Halo Surface Signal indicates that because Budibase applications are frequently deployed as internet-facing web portals, they are often reachable via the public web. If your deployment uses the affected MySQL integration and is accessible to external users, it faces a higher likelihood of being reachable for this type of injection attack.

How do I secure my environment?

Your first step is to identify all Budibase instances within your infrastructure and verify their version. Since this vulnerability is resolved in version 3.40.0, upgrading to this or a newer release is the primary fix. Coordinate with the teams managing these deployments to audit their configuration and apply the update immediately.

References