{"answers":{"affected":"2 open source packages ship an affected version, including billabear/billabear.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31069 exists.","fix":"No fix has been published for CVE-2026-31069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31069 is a high-severity SQL injection vulnerability in n/a, published on 19 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-31069 and fix it if it is affected.\n\nWhat it is: CVE-2026-31069 is a high-severity SQL injection vulnerability in n/a, published on 19 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-31069 exists.\n\nAffected packages and fixed versions:\n- billabear/billabear (Packagist): affected all versions up to 2025.01.03; no fix listed\n- billabear/billabear (Packagist): affected all versions up to 2025.01.03; 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-31069/ (Markdown: https://insights.sbomify.com/CVE-2026-31069/index.md)","id":"CVE-2026-31069","markdown":"https://insights.sbomify.com/CVE-2026-31069/index.md","name":"CVE-2026-31069","record":{"aliases":["GHSA-xp6r-8pcc-xv5p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"BillaBear billing software","requires_auth":"low_privilege","summary":"An authenticated attacker can execute arbitrary SQL commands via unsanitized filter identifiers in BillaBear, potentially accessing or modifying data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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":"BillaBear (all versions prior to Jan 2026) contains a SQL Injection vulnerability in the EventRepository. User-controlled input from metric filter names and aggregation properties is directly interpolated into SQL queries using sprintf() without proper sanitization or identifier quoting. Although filter values are parameterized, the filter identifiers (keys) are not. An authenticated attacker with ROLE_ACCOUNT_MANAGER permissions can exploit this to execute arbitrary SQL commands.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"BillaBear is Vulnerable to SQL Injection in the EventRepository","id":"CVE-2026-31069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2026-31070"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2025.01.03"],"package":"billabear/billabear","purl":null,"source":"GHSA-xp6r-8pcc-xv5p"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2025.01.03"],"package":"billabear/billabear","purl":"pkg:composer/billabear/billabear","source":"GHSA-xp6r-8pcc-xv5p"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2026-31067"},"products":["n/a"],"published":"2026-05-19","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["n/a"]},"summary":"An authenticated attacker can execute arbitrary SQL commands via unsanitized filter identifiers in BillaBear, potentially accessing or modifying data.","url":"https://insights.sbomify.com/CVE-2026-31069/"}