{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0603 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0603 is a critical SQL injection vulnerability in Callvision Emergency Code, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-0603 and fix it if it is affected.\n\nWhat it is: CVE-2025-0603 is a critical SQL injection vulnerability in Callvision Emergency Code, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-0603 in the wild and no public exploit code.\n\nAffected product: Callvision Emergency Code. 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-2025-0603/ (Markdown: https://insights.sbomify.com/CVE-2025-0603/index.md)","id":"CVE-2025-0603","markdown":"https://insights.sbomify.com/CVE-2025-0603/index.md","name":"CVE-2025-0603","record":{"aliases":["GHSA-x8q5-wfwx-9652"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Healthcare emergency software","requires_auth":"none","summary":"Attackers can execute SQL injection attacks in Callvision Emergency Code to read or modify database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TR-CERT","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Callvision Healthcare Callvision Emergency Code allows SQL Injection, Blind SQL Injection.\n\nThis issue affects Callvision Emergency Code: before V3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQLi in Callvision Healthcare's Callvision Emergency Code","id":"CVE-2025-0603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Keycloak-ldap-federation: authentication bypass due to missing ldap bind after password reset in keycloak","id":"CVE-2025-0604"},"packages":[],"prev":{"headline":"Cross-site scripting in Collaborative Industry Innovator","id":"CVE-2025-0602"},"products":["Callvision Emergency Code"],"published":"2025-10-07","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-06","vendors":["Callvision Healthcare"]},"summary":"Attackers can execute SQL injection attacks in Callvision Emergency Code to read or modify database information.","url":"https://insights.sbomify.com/CVE-2025-0603/"}