CVE-2025-14960
SQL Injection in Simple Blood Donor Management System /editeddonor.php
Publication date: 2025-12-19
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 |
|---|---|---|
| code-projects | simple_blood_donor_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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and leakage of sensitive data due to SQL injection, which can lead to violations of data protection regulations such as GDPR and HIPAA. These regulations require the protection of personal and health information from unauthorized access and breaches. Exploitation of this vulnerability compromises confidentiality, integrity, and availability of data, thereby negatively impacting compliance with such standards. Immediate remediation is necessary to maintain data security and regulatory compliance. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-14960 is a critical SQL injection vulnerability in version 1.0 of the Simple Blood Donor Management System, specifically in the /editeddonor.php file. The vulnerability occurs because the application improperly handles the 'Name' parameter, allowing attackers to inject malicious SQL code without proper input validation or sanitization. This enables attackers to execute arbitrary SQL commands remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, and full system control. [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, modification or deletion of data, disruption of services, and potentially full control over the affected system. Since no authentication is required to exploit it, attackers can remotely execute malicious SQL commands, compromising the confidentiality, integrity, and availability of the 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 'name' parameter in the /simpleblooddonor/editeddonor.php file for SQL injection using boolean-based blind or time-based blind SQL injection techniques. Example payloads include: `name=Leibai' RLIKE (SELECT (CASE WHEN (6827=6827) THEN 0x4c6569626169 ELSE 0x28 END))--` and `name=Leibai' RLIKE SLEEP(5)--`. Tools like sqlmap can be used to automate detection and exploitation attempts. Additionally, Google dorking with the query `inurl:editeddonor.php` can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: using prepared statements with parameter binding to separate SQL code from user input; implementing strict input validation and filtering to ensure inputs conform to expected formats; minimizing database user permissions by avoiding high-privilege accounts for routine operations; conducting regular security audits to detect and fix vulnerabilities promptly; and considering replacing the affected component with an alternative product. [1, 3]