CVE-2026-10185
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
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?
This vulnerability is a SQL injection issue found in the SourceCodester Hospitals Patient Records Management System 1.0, specifically in the file /classes/Users.php with the function parameter f=save. It occurs due to improper input validation of the 'id' parameter, which allows an attacker to manipulate the SQL queries executed by the system.
Because of this flaw, an attacker can inject malicious SQL code remotely without needing authentication, potentially gaining unauthorized access to the database.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to several serious impacts including unauthorized access to sensitive patient data, data leakage, data tampering, and potentially full control over the affected system.
Additionally, attackers could disrupt system availability, causing denial of service or other interruptions to hospital operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in /classes/Users.php?f=save can be detected by testing the 'id' parameter for injection flaws.
One common method is to use automated tools such as sqlmap to test for SQL injection by targeting the vulnerable URL parameter.
- Example sqlmap command: sqlmap -u "http://targetsite/classes/Users.php?f=save&id=1" --batch
- Manually, you can try injecting SQL syntax into the 'id' parameter, such as appending a single quote (') or SQL keywords, and observe if errors or unexpected behavior occur.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements (parameterized queries) to prevent SQL injection.
- Validate and sanitize all user inputs, especially 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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows unauthorized access, data leakage, and tampering with patient records in the Hospital's Patient Records Management System. Such unauthorized access and data breaches can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and health information against unauthorized disclosure and alteration.
Failure to protect patient data adequately may result in violations of confidentiality, integrity, and availability requirements mandated by these standards, potentially leading to legal penalties and loss of trust.