CVE-2025-14961
SQL Injection in Simple Blood Donor Management System Allows Remote Exploit
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14961 is a critical SQL injection vulnerability in the Simple Blood Donor Management System version 1.0, specifically in the file /editedcampaign.php. It occurs because the application improperly handles the 'campaignname' parameter, using it directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating database queries to access, modify, or delete data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and full system control by attackers. It can also cause service disruption. Since exploitation requires no authentication and can be done remotely, attackers can easily compromise the system's confidentiality, integrity, and availability, potentially leading to significant security breaches and operational impact. [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 affected endpoint `/editedcampaign.php` for SQL injection via the `campaignname` parameter. A known proof-of-concept payload is: `campaignname=Leibai' RLIKE (SELECT (CASE WHEN (8193=8193) THEN 0x4c6569626169 ELSE 0x28 END))--`. You can use tools like sqlmap to automate detection, for example: `sqlmap -u "http://target/editedcampaign.php" --data="campaignname=Leibai" --risk=3 --level=5`. Additionally, searching for the vulnerable URL pattern using Google dorking such as `inurl:editedcampaign.php` can help identify exposed targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input. 2) Apply strict input validation and filtering on the `campaignname` parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, data leakage, and data tampering due to SQL injection, which can lead to breaches of confidentiality and integrity of sensitive data. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and health information against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could negatively impact compliance with these standards. [1, 2, 3]