CVE-2025-5857
BaseFortify
Publication date: 2025-06-09
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabianros | patient_record_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-2025-5857 is a critical SQL injection vulnerability in the code-projects Patient Record Management System 1.0, specifically in the file /urinalysis_record.php. The vulnerability occurs because the parameter itr_no is directly used in an SQL query without proper input validation or sanitization. This allows an attacker to inject malicious SQL code remotely, potentially accessing or manipulating sensitive patient data stored in the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to remotely execute SQL injection attacks on the Patient Record Management System, leading to unauthorized access, disclosure, modification, or deletion of sensitive patient information. It affects the confidentiality, integrity, and availability of the system, potentially exposing confidential medical data and disrupting system operations. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file urinalysis_record.php and testing the itr_no parameter for SQL injection. One method is to use Google dorking with the query `inurl:urinalysis_record.php` to identify potentially vulnerable targets. For direct testing, you can use curl or similar tools to send crafted requests to the parameter itr_no and observe if SQL errors or unexpected behavior occur. Example command: `curl -G 'http://target/urinalysis_record.php' --data-urlencode 'itr_no=1 OR 1=1'`. If the response indicates SQL errors or returns unauthorized data, the system is likely vulnerable. [2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. The recommended immediate step is to replace the affected product with a secure version or alternative software. Additionally, restricting access to the vulnerable endpoint and monitoring for suspicious activity may help reduce risk until a fix is applied. [2]