{"answers":{"affected":"2 open source packages ship an affected version, including @budibase/server.","exploited":"There is no known exploitation of CVE-2026-73408 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73408 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73408 is a high-severity SQL injection vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-73408 and fix it if it is affected.\n\nWhat it is: CVE-2026-73408 is a high-severity SQL injection vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-73408 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed\n- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73408/ (Markdown: https://insights.sbomify.com/CVE-2026-73408/index.md)","id":"CVE-2026-73408","markdown":"https://insights.sbomify.com/CVE-2026-73408/index.md","name":"CVE-2026-73408","record":{"aliases":["GHSA-2xgg-r2wc-c5r2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"high_privilege","summary":"Attacker can execute arbitrary SQL via stacked queries in table names during schema discovery, requiring admin interaction.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Budibase is an open-source low-code platform. Prior to 3.39.18, packages/server/src/integrations/mysql.ts enabled multipleStatements and inserted an unescaped tableName into a DESCRIBE statement. An attacker able to create a MySQL table with a backtick and stacked statement in its name could wait for a Budibase administrator to run schema discovery, causing the second statement to execute. The fix applies quoteMySqlIdentifier before constructing the query. This issue is fixed in version 3.39.18.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Budibase: MySQL DESCRIBE Backtick Injection via multipleStatements in Database Connector","id":"CVE-2026-73408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Budibase: Server Filesystem Existence/Read Oracle via Builder-Controlled MongoDB tlsCertificateKeyFile","id":"CVE-2026-73409"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":null,"source":"GHSA-2xgg-r2wc-c5r2"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":"pkg:npm/%40budibase/server","source":"GHSA-2xgg-r2wc-c5r2"}],"prev":{"headline":"Budibase: Unauthenticated REST Datasource Credential Theft via Cross-Origin Auth Leak (bypass of CVE-2026-48152))","id":"CVE-2026-73407"},"products":["budibase"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["Budibase"]},"summary":"Attacker can execute arbitrary SQL via stacked queries in table names during schema discovery, requiring admin interaction.","url":"https://insights.sbomify.com/CVE-2026-73408/"}