Critical SQL Injection Vulnerability Reported in Budibase MySQL Integration
An early warning has been issued regarding a critical SQL injection vulnerability reportedly discovered in Budibase's MySQL integration, which could allow remote attackers to execute arbitrary SQL commands.
What happened
According to the initial reports, the vulnerability appears to be related to the `multipleStatements` setting in Budibase's MySQL integration. When `multipleStatements` is set to `true`, it may enable SQL injection attacks. Budibase has released updates to address this issue, with versions 3.38.1, 3.30.4, 3.35.10, 3.38.2, 3.39.0, and 3.39.19 containing fixes.
To assess your exposure, check the version of Budibase you are currently using. If you are running a version lower than those listed above as fixed, it is recommended to upgrade to the latest version immediately. Additionally, ensure that the `multipleStatements` setting is configured to `false` to mitigate the risk of exploitation.
For more detailed information and to verify the status of this vulnerability, consult the primary sources provided, including the GitHub Security Advisories [GHSA-2xgg-r2wc-c5r2], [GHSA-4qcj-m5wp-jmf4], [GHSA-hp6v-6jw7-gv2f], [GHSA-mqhr-6j6h-74p5], and [GHSA-q6x4-v3qx-85qw].
How 0Day mitigates this
budibase is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.