CVE-2026-10184
SQL Injection in Hospitals Patient Records Management System
Publication date: 2026-05-31
Last updated on: 2026-05-31
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | hospitals_patient_records_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-10184 is a SQL injection vulnerability found in the SourceCodester Hospitals Patient Records Management System version 1.0, specifically in the file /classes/Users.php?f=delete.
The vulnerability occurs because the 'id' parameter is not properly validated, allowing an attacker to inject malicious SQL queries remotely without authentication.
Attackers can exploit this flaw using techniques such as boolean-based blind, time-based blind, and UNION query injections to manipulate the database.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to tamper with data and leak sensitive information.
This may result in a full system compromise, affecting the integrity, confidentiality, and availability of the patient records management system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /classes/Users.php?f=delete endpoint for SQL injection flaws. Attackers may use boolean-based blind, time-based blind, and UNION query techniques to exploit it.
To detect the vulnerability, you can use SQL injection testing tools or manual commands such as:
- Using curl to test for SQL injection by injecting a single quote: curl "http://target/classes/Users.php?f=delete&id=1'"
- Using sqlmap to automate detection: sqlmap -u "http://target/classes/Users.php?f=delete&id=1" --batch
- Manually testing with time-based payloads to observe delays, e.g., appending ' AND SLEEP(5)-- ' to the id parameter.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameterized queries to prevent SQL injection.
- Apply strict input validation and sanitization on the 'id' parameter.
- Minimize database user permissions to limit the impact of a potential exploit.
- Conduct regular security audits and code reviews to identify and fix vulnerabilities.
- If possible, restrict or monitor access to the vulnerable endpoint to detect or block malicious requests.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Hospital's Patient Records Management System allows unauthorized database access, data tampering, and sensitive information leakage. Such unauthorized access and exposure of sensitive patient data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate strict controls over personal and health information to ensure confidentiality, integrity, and availability.
Failure to address this vulnerability could result in violations of these standards, potentially causing legal penalties, loss of patient trust, and damage to the organization's reputation.