CVE-2026-111990: Hospital Mgmt System: SQL injection in appointment cancel
HIGHCISA: TRACK*A SQL injection flaw in the open-source kishan0725 Hospital Management System lets a remote, unauthenticated attacker manipulate the ID parameter of the appointment cancellation handler in admin-panel.php and run arbitrary queries against the backend database. Despite the 'ml_ui' tag, this is a conventional PHP/MySQL web application with no evident AI/ML functionality, so the AI-specific blast radius is minimal. The CVSS score is 7.3 (high) and EPSS is low at 0.00254 (84th percentile). The CVE is not in CISA KEV and has no Nuclei template. A proof of concept is described in the public GitHub issue and the maintainer has not responded, so no patch should be expected. Organizations running this project, typically as a demo or student deployment, should take it offline or put it behind a WAF and authentication. If it is in use, replace the vulnerable mysqli_query call with prepared statements and check for any patient data exposure.
What is the risk?
Rated high on the CVSS side (7.3, network-reachable, no privileges, no user interaction, low impact on confidentiality, integrity and availability). Real-world risk is moderate: the EPSS score is low, there is no KEV listing or scanner template, but a public exploit reference exists and the project is unmaintained with no fix. The exposure is greatest where the application holds real patient data. The AI/ML relevance is negligible and the 'ml_ui' classification looks like a false positive.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| Hospital Management System | — | — | No patch |
Do you use Hospital Management System? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) No vendor patch is available and the maintainer has not responded, so remove the application from internet exposure or restrict it to trusted networks. 2) Refactor the vulnerable code to use parameterized queries (mysqli prepared statements) and validate the ID parameter as an integer. 3) Deploy WAF rules that block SQL injection patterns on admin-panel.php. 4) Run the database account with least privilege (no FILE, no DDL). 5) Review web and database logs for anomalous ID values, UNION/SLEEP payloads, and unexpected query errors. 6) If real patient data was handled, assess for a breach under applicable regulations (GDPR/HIPAA) and rotate credentials. 7) Consider migrating to a maintained alternative.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-111990?
A SQL injection flaw in the open-source kishan0725 Hospital Management System lets a remote, unauthenticated attacker manipulate the ID parameter of the appointment cancellation handler in admin-panel.php and run arbitrary queries against the backend database. Despite the 'ml_ui' tag, this is a conventional PHP/MySQL web application with no evident AI/ML functionality, so the AI-specific blast radius is minimal. The CVSS score is 7.3 (high) and EPSS is low at 0.00254 (84th percentile). The CVE is not in CISA KEV and has no Nuclei template. A proof of concept is described in the public GitHub issue and the maintainer has not responded, so no patch should be expected. Organizations running this project, typically as a demo or student deployment, should take it offline or put it behind a WAF and authentication. If it is in use, replace the vulnerable mysqli_query call with prepared statements and check for any patient data exposure.
Is CVE-2026-111990 actively exploited?
No confirmed active exploitation of CVE-2026-111990 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-111990?
1) No vendor patch is available and the maintainer has not responded, so remove the application from internet exposure or restrict it to trusted networks. 2) Refactor the vulnerable code to use parameterized queries (mysqli prepared statements) and validate the ID parameter as an integer. 3) Deploy WAF rules that block SQL injection patterns on admin-panel.php. 4) Run the database account with least privilege (no FILE, no DDL). 5) Review web and database logs for anomalous ID values, UNION/SLEEP payloads, and unexpected query errors. 6) If real patient data was handled, assess for a breach under applicable regulations (GDPR/HIPAA) and rotate credentials. 7) Consider migrating to a maintained alternative.
What systems are affected by CVE-2026-111990?
This vulnerability affects the following AI/ML architecture patterns: Web applications (PHP/MySQL), Healthcare management systems, Data stores feeding analytics pipelines.
What is the CVSS score for CVE-2026-111990?
CVE-2026-111990 has a CVSS v3.1 base score of 7.3 (HIGH). The EPSS exploitation probability is 0.25%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
What are the technical details?
Original Advisory
A weakness has been identified in kishan0725 Hospital Management System up to 777fda46b77a820977a5ba616283dbfbc40bf7e1. This affects the function mysqli_query of the file admin-panel.php of the component Appointment Cancellation Handler. Executing a manipulation of the argument ID can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
Exploitation Scenario
An attacker finds an internet-exposed instance of the Hospital Management System via search engines or scanning, then follows the public GitHub issue to send a crafted ID value to the appointment cancellation endpoint in admin-panel.php. Using UNION-based or blind SQL injection, they dump user and patient tables, extract credentials, and may alter appointment data. If any analytics or ML workflow consumes that database, the attacker could also poison its inputs, though that is a secondary, speculative impact.
Weaknesses (CWE)
CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CWE-74 — Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'): The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
- [Requirements] Programming languages and supporting technologies might be chosen which are not subject to these issues.
- [Implementation] Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:CReferences
- github.com/kishan0725/Hospital-Management-System/issues/75exploitissue-tracking
- vuldb.com/cve/CVE-2026-111990third-party-advisory
- vuldb.com/submit/1007402third-party-advisory
- vuldb.com/vuln/421655vdb-entrytechnical-description
- vuldb.com/vuln/421655/ctisignaturepermissions-required
Timeline
Related Vulnerabilities
CVE-2025-512010.0smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Data LeakageCVE-2023-376510.0MLflow: path traversal allows arbitrary file read
Same attack type: Data LeakageCVE-2025-282810.0LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth BypassCVE-2025-5376710.0Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Auth BypassCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same attack type: Auth Bypass