CVE-2025-41004
SQL Injection in Imaster Patient Records 'complaints.php' Endpoint
Publication date: 2026-01-12
Last updated on: 2026-01-12
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imaster | patient_records_management_system | * |
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. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the '/projects/hospital/admin/complaints.php' endpoint for SQL Injection via the 'id' parameter. You can use tools like sqlmap or manual curl commands to test for SQL Injection. For example, using curl: curl -v 'http://<target>/projects/hospital/admin/complaints.php?id=1' and then try injecting SQL payloads such as '1 OR 1=1' or '1' UNION SELECT NULL-- to observe if the response indicates SQL Injection. Automated scanners that test for SQL Injection vulnerabilities can also be used.
Can you explain this vulnerability to me?
This vulnerability is a SQL Injection in Imaster's Patient Records Management System. It occurs in the endpoint '/projects/hospital/admin/complaints.php' through the 'id' parameter. An attacker can exploit this by injecting malicious SQL code via the 'id' parameter, potentially manipulating the database queries executed by the system.
How can this vulnerability impact me? :
The SQL Injection vulnerability can allow an attacker to access, modify, or delete sensitive patient data stored in the system's database. This can lead to data breaches, loss of data integrity, unauthorized data disclosure, and potentially disrupt the normal operation of the Patient Records Management System.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and sanitizing the 'id' parameter input on the server side to prevent SQL Injection. Use parameterized queries or prepared statements in the code handling this endpoint. Additionally, restrict database user permissions to limit the impact of a potential injection. If possible, apply any available patches or updates from the vendor addressing this vulnerability.