CVE-2022-23366 json
HMS v1.0 was discovered to contain a SQL injection vulnerability via patientlogin.php.
published 4y ago modified 4mo ago also EUVD-2022-28445
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.8%
- EPSS 6.8% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
HMS v1.0 was discovered to contain a SQL injection vulnerability via patientlogin.php.
Is CVE-2022-23366 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 FencerTimeline
- Published
- First public exploit (EDB-50729)
Exploit prediction
6.76% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50729 Hospital Management Startup 1.0 - 'Multiple' SQLi webapps, 2022-02-10
- github.com https://github.com/kabirkhyrul/HMS/discussions/4 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/nu11secur1ty/CVE-mitre/tree/main/2022/CVE-2022-23366 referenced PoC, tagged "exploit" by a source, unverified
- nu11secur1ty.com https://www.nu11secur1ty.com/2022/02/cve-2022-23366.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/kabirkhyrul/HMS/discussions/4
exploit, third-party-advisory
-
github.com
/nu11secur1ty/CVE-mitre/tree/main/2022/CVE-2022-23366
exploit, third-party-advisory
-
nu11secur1ty.com
/2022/02/cve-2022-23366.html
exploit, third-party-advisory
-
packetstormsecurity.com
/files/165948/Hospital-Management-Startup-1.0-SQL-Injection.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-23366
- NVD CVE-2022-23366
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.