CVE-2025-0603 json
SQLi in Callvision Healthcare's Callvision Emergency Code
published last yr. modified last mo. also EUVD-2025-32097
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
This issue affects Callvision Emergency Code: before V3.0.
Patch / fix
- Callvision Healthcare Callvision Emergency Code V3.0
Is CVE-2025-0603 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Callvision Healthcare Callvision Emergency Code
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
usom.gov.tr
/bildirim/tr-25-0320
government-resource, broken-link
-
siberguvenlik.gov.tr
/guvenlik-bildirimleri/detay/tr-25-0320
government-resource
Sources
- CVE List CVE-2025-0603
- NVD CVE-2025-0603
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.