CVE-2025-5602
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-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-5602 is a critical SQL Injection vulnerability in Campcodes Hospital Management System version 1.0, specifically in the /admin/registration.php file. The vulnerability occurs due to improper handling of the 'full_name' parameter, allowing an attacker to inject malicious SQL code remotely without authentication. This can enable execution of arbitrary SQL commands, potentially leading to unauthorized access or control over the system. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary SQL commands on the affected system, potentially leading to unauthorized access, data leakage, modification, or deletion of sensitive information. It compromises the confidentiality, integrity, and availability of the hospital management system, which could disrupt operations and expose sensitive patient data. [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 endpoint /admin/registration.php and testing the full_name parameter for SQL injection. One method is to use Google dorking with the query "inurl:admin/registration.php" to identify potentially vulnerable targets. For direct testing, you can use tools like sqlmap or manual curl commands to inject SQL payloads into the full_name parameter and observe the response for SQL errors or unexpected behavior. Example curl command: curl -G 'http://target/admin/registration.php' --data-urlencode 'full_name=admin' OR '1'='1'. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /admin/registration.php endpoint, applying input validation and sanitization on the full_name parameter to prevent SQL injection, and considering replacing the affected product as no known countermeasures or patches are currently identified. Additionally, monitoring for suspicious activity and applying web application firewalls (WAF) rules to block SQL injection attempts can help reduce risk until a permanent fix is available. [2]