CVE-2025-5716
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-5716 is a critical SQL injection vulnerability in the SourceCodester Open Source Clinic Management System version 1.0, specifically in the /login.php file. The vulnerability occurs because the application does not properly validate or sanitize the 'email' parameter, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, potentially allowing attackers to manipulate, delete, or expose sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, exposure of sensitive information, modification or deletion of data, full system compromise, and disruption of service availability. Since exploitation requires no authentication and can be performed remotely, attackers can easily exploit this flaw to damage the system and compromise data integrity and confidentiality. [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 'email' parameter in the /login.php file for SQL injection. You can use SQL injection testing tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/login.php" --data="[email protected]&password=any" -p email --batch. Additionally, manual testing with payloads such as 'email=1' OR NOT 8398=8398 #' or time-based payloads like 'email=1' AND (SELECT SLEEP(5))--' can help identify the vulnerability by observing abnormal responses or delays. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'email' parameter, and minimizing database user privileges by avoiding use of high-privilege accounts for routine operations. Since no official patches or countermeasures are reported, replacing the affected product with a secure alternative is also suggested. Conducting regular security audits is recommended to detect and address vulnerabilities promptly. [1, 3, 2]