CVE-2025-5712
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-5712 is a critical SQL injection vulnerability in the SourceCodester Open Source Clinic Management System version 1.0, specifically in the /appointment.php file. The vulnerability occurs because the 'patient' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data leakage, modification, deletion, or even full system compromise. The attack can be performed remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, modification or deletion of database records, and disruption of system availability. Attackers can remotely execute arbitrary SQL commands, potentially compromising the confidentiality, integrity, and availability of the system. This can result in data breaches, loss of data integrity, and service disruptions. [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 'patient' parameter in the /appointment.php file for SQL injection. One method is to use sqlmap, an automated SQL injection tool, to test the endpoint with the vulnerable parameter. For example, a command like `sqlmap -u "http://target/appointment.php" --data="patient=1"` can be used to test injection. Additionally, a time-based blind SQL injection payload such as `1' OR '1' AND 6924=BENCHMARK(5000000,MD5(0x476f426a))--` can be sent in a POST request to observe delays indicating vulnerability. Google dorking with queries like `inurl:appointment.php` can help identify vulnerable targets on the network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'patient' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. Since no patches or known mitigations are currently available, consider replacing the affected component with an alternative product if possible. [1, 3, 2]