{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-61851 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-61851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-61851 is a medium-severity SQL injection vulnerability in chartbrew, published on 21 Sep 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-61851 and fix it if it is affected.\n\nWhat it is: CVE-2026-61851 is a medium-severity SQL injection vulnerability in chartbrew, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61851 in the wild and no public exploit code.\n\nAffected product: chartbrew. 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-61851/ (Markdown: https://insights.sbomify.com/CVE-2026-61851/index.md)","id":"CVE-2026-61851","markdown":"https://insights.sbomify.com/CVE-2026-61851/index.md","name":"CVE-2026-61851","record":{"aliases":["GHSA-cp8j-2xwc-hxg8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Chartbrew web application","requires_auth":"low_privilege","summary":"Authenticated users can bypass read-only restrictions in Chartbrew's AI tool to execute arbitrary SQL, leading to data exposure, modification, or command execution.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.2, Chartbrew's runQuery() implementation in server/modules/ai/orchestrator/tools/runQuery.js attempts to enforce read-only database access with a blocklist containing only seven SQL keywords. An authenticated user with AI feature access can submit dangerous statements or database functions that are absent from the read-only keyword blocklist, causing them to execute without SQL injection or keyword-obfuscation techniques. Depending on the database engine, configuration, and database-user privileges, this can expose or write files, access internal network resources, change database privileges, execute commands, or alter data. This issue is fixed in version 5.2.2.","ecosystems":[],"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":"Chartbrew: Incomplete Read-Only Keyword Blocklist in AI runQuery Tool","id":"CVE-2026-61851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Chartbrew: SQL Injection via row_limit Parameter in AI runQuery Tool","id":"CVE-2026-61852"},"packages":[],"prev":{"headline":"FileRise: Folder Metadata Filename Collisions Bypass \"read_own\" Isolation","id":"CVE-2026-61844"},"products":["chartbrew"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["chartbrew"]},"summary":"Authenticated users can bypass read-only restrictions in Chartbrew's AI tool to execute arbitrary SQL, leading to data exposure, modification, or command execution.","url":"https://insights.sbomify.com/CVE-2026-61851/"}