CVE-2025-5604
BaseFortify
Publication date: 2025-06-04
Last updated on: 2025-06-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| campcodes | online_hospital_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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
Can you explain this vulnerability to me?
CVE-2025-5604 is a critical SQL injection vulnerability in Campcodes Hospital Management System version 1.0, specifically in the /user-login.php file. The vulnerability occurs because the application does not properly neutralize special characters in the 'username' parameter, allowing an attacker to inject malicious SQL code. This flaw can be exploited remotely without authentication, enabling attackers to manipulate the database through crafted input, potentially compromising the system's confidentiality, integrity, and availability. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to remotely execute arbitrary SQL commands on the hospital management system's database without authentication. This can lead to unauthorized access to sensitive patient and hospital data, modification or deletion of records, and disruption of system availability. The impact includes loss of confidentiality, integrity, and availability of the system, potentially causing severe operational and reputational damage. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /user-login.php endpoint for SQL injection via the 'username' parameter. You can use tools like curl or sqlmap to test for SQL injection. For example, using curl: curl -v "http://targetsite/user-login.php?username=' OR '1'='1" to see if the response indicates SQL injection. Alternatively, sqlmap can be used: sqlmap -u "http://targetsite/user-login.php" --data="username=anything" -p username --batch. Additionally, Google Hacking techniques such as searching for inurl:user-login.php can help identify potentially vulnerable targets. [1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. The suggested immediate step is to replace the affected product with an alternative solution to avoid exploitation. [1]