{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14603 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14603 is a high-severity SQL injection vulnerability in vsDesk, published on 19 Aug 2026. 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-14603 and fix it if it is affected.\n\nWhat it is: CVE-2025-14603 is a high-severity SQL injection vulnerability in vsDesk, published on 19 Aug 2026. 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-14603 in the wild and no public exploit code.\n\nAffected product: vsDesk. 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-14603/ (Markdown: https://insights.sbomify.com/CVE-2025-14603/index.md)","id":"CVE-2025-14603","markdown":"https://insights.sbomify.com/CVE-2025-14603/index.md","name":"CVE-2025-14603","record":{"aliases":["GHSA-76p9-g6m2-hj7q"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"vsDesk helpdesk","requires_auth":"none","summary":"Blind SQL injection in vsDesk allows attackers to read database contents or cause denial of service via insecure user input handling.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Kaspersky","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[],"description":"The application component processes user-supplied parameters insecurely, passing them into SQL queries. This can enable blind SQL injection, potentially exposing database contents or causing the application to become unresponsive. \nApply patch from vendor  https://vsdesk.ru/ . Versions 14.0101 and on have the patch.","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":"Use of user input in raw SQL queries in vsDesk leading to blind SQL injection","id":"CVE-2025-14603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Storage Scale","id":"CVE-2025-14604"},"packages":[],"prev":{"headline":"Weak File Name Generation in vsDesk","id":"CVE-2025-14602"},"products":["vsDesk"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["vsDesk"]},"summary":"Blind SQL injection in vsDesk allows attackers to read database contents or cause denial of service via insecure user input handling.","url":"https://insights.sbomify.com/CVE-2025-14603/"}