{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33324 exists.","fix":"No fix has been published for CVE-2026-33324 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33324 is a critical SQL injection vulnerability in dataease SQLBot, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33324 and fix it if it is affected.\n\nWhat it is: CVE-2026-33324 is a critical SQL injection vulnerability in dataease SQLBot, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33324 exists.\n\nAffected product: dataease SQLBot. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-33324/ (Markdown: https://insights.sbomify.com/CVE-2026-33324/index.md)","id":"CVE-2026-33324","markdown":"https://insights.sbomify.com/CVE-2026-33324/index.md","name":"CVE-2026-33324","record":{"aliases":["GHSA-q2q6-gqqh-4xrx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Text-to-SQL system","requires_auth":"low_privilege","summary":"An authenticated attacker can exploit prompt injection in SQLBot to execute arbitrary SQL and achieve remote code execution via PostgreSQL.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sqlbot","vendor":"fit2cloud"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. In versions 1.7.0 and earlier, the Text2SQL chat interface is vulnerable to prompt injection. The user-provided question parameter is directly concatenated into the LLM prompt without filtering or escaping, and the SQL extracted from the LLM response is executed against the database without validation or sanitization. An authenticated attacker can craft a malicious question to manipulate the LLM into generating and executing arbitrary SQL statements. When connected to a PostgreSQL data source, this can lead to remote code execution via COPY FROM PROGRAM. This issue has been fixed in version 1.7.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SQLBot prompt injection allows arbitrary SQL execution and remote code execution","id":"CVE-2026-33324","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"@keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany","id":"CVE-2026-33326"},"packages":[],"prev":{"headline":"Parse Server: Email verification resend page leaks user existence","id":"CVE-2026-33323"},"products":["SQLBot"],"published":"2026-05-05","related":[{"cvss_score":8.7,"headline":"SQLBot: SSRF to Arbitrary File Read (AFR) via Rogue MySQL","id":"CVE-2026-32949","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.6,"headline":"SQLBot: Unauthorized Access Vulnerability","id":"CVE-2026-42463","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":8.6,"headline":"SQLBot: RCE via SQL Injection in Excel Upload Endpoint","id":"CVE-2026-32950","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.6,"headline":"SQLBot: Remote Code Execution via Terminology Poisoning","id":"CVE-2026-32622","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":7.7,"headline":"SQLBot uploadExcel Endpoint has Unauthenticated Arbitrary File Upload vulnerability","id":"CVE-2025-69285","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":6.3,"headline":"Dataease SQLBot JWT Token auth.py validateEmbedded signature verification","id":"CVE-2025-15598","kev_date_added":null,"published":"2026-03-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-05","vendors":["dataease"]},"summary":"An authenticated attacker can exploit prompt injection in SQLBot to execute arbitrary SQL and achieve remote code execution via PostgreSQL.","url":"https://insights.sbomify.com/CVE-2026-33324/"}