CVE-2025-6406
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-21

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability, which was classified as critical, has been found in Campcodes Online Hospital Management System 1.0. Affected by this issue is some unknown functionality of the file /hms/forgot-password.php. The manipulation of the argument fullname leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-21
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-06-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
campcodes online_hospital_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-6406 is a critical SQL injection vulnerability in Campcodes Online Hospital Management System version 1.0, specifically in the /hms/forgot-password.php file. The vulnerability occurs due to improper handling and inadequate validation of the 'fullname' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data retrieval, modification, deletion, and exposure of sensitive information. [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, alteration or deletion of data, full system compromise, and disruption of service availability. Since the vulnerability can be exploited remotely without authentication, attackers can easily launch attacks leading to confidentiality, integrity, and availability breaches. [1, 2, 3]


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 /hms/forgot-password.php and testing the 'fullname' parameter for SQL injection. One method is to use Google dorking with the query: inurl:hms/forgot-password.php to identify potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to send payloads to the 'fullname' parameter and observe for SQL errors or unexpected behavior. Specific commands could include using curl or sqlmap, for example: curl -G 'http://target/hms/forgot-password.php' --data-urlencode "fullname=' OR '1'='1" or sqlmap -u "http://target/hms/forgot-password.php?fullname=test" --risk=3 --level=5 to test for injection. [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: 1) Implementing prepared statements or parameterized queries to safely handle the 'fullname' input and prevent SQL injection. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conducting regular security audits of code and systems to detect and remediate vulnerabilities promptly. If possible, replacing the affected product with a secure alternative is recommended as no known countermeasures or patches are currently reported. [2, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart