CVE-2025-5758
BaseFortify
Publication date: 2025-06-06
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 |
|---|---|---|
| nikhil-bhalerao | open_source_clinic_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-5758 is a critical SQL injection vulnerability in the SourceCodester Open Source Clinic Management System version 1.0, specifically in the /doctor.php file. The vulnerability arises from improper handling of the 'doctorname' parameter, which allows attackers to inject malicious SQL code due to inadequate input validation or sanitization. This enables attackers to execute unauthorized SQL queries remotely without authentication, potentially accessing, modifying, or deleting sensitive database information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete data, and potentially cause full system compromise or service disruption. Since it can be exploited remotely without authentication and has publicly available proof-of-concept exploits, it poses a significant risk to the confidentiality, integrity, and availability of the affected system. [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 testing the 'doctorname' parameter in the /doctor.php endpoint for SQL injection flaws. Tools like sqlmap have been successfully used to confirm the vulnerability by enumerating databases through crafted requests targeting this parameter. You can use sqlmap with a command such as: sqlmap -u "http://target/doctor.php" --data="doctorname=anything" --risk=3 --level=5 to test for SQL injection. Additionally, error-based and time-based blind SQL injection payloads can be sent via POST requests to observe database responses or delays indicating vulnerability. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'doctorname' parameter and other inputs, and minimizing database user privileges to the least necessary. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended as no known countermeasures are documented. [2, 3]