Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14960: SQL Injection in code-projects Simple Blood Donor Management System

0
Medium
VulnerabilityCVE-2025-14960cvecve-2025-14960
Published: Fri Dec 19 2025 (12/19/2025, 18:02:08 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Simple Blood Donor Management System

Description

A security vulnerability has been detected in code-projects Simple Blood Donor Management System 1.0. Impacted is an unknown function of the file /editeddonor.php. The manipulation of the argument Name leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used.

AI-Powered Analysis

AILast updated: 12/19/2025, 18:30:20 UTC

Technical Analysis

CVE-2025-14960 identifies a SQL injection vulnerability in the Simple Blood Donor Management System version 1.0, specifically within the /editeddonor.php file. The vulnerability arises from improper handling of the 'Name' parameter, which is directly incorporated into SQL queries without adequate sanitization or use of parameterized statements. This allows remote attackers to inject arbitrary SQL commands, potentially enabling unauthorized data access, modification, or deletion within the backend database. The attack vector requires no authentication or user interaction, increasing the risk profile. The CVSS 4.0 score of 6.9 (medium severity) reflects the network attack vector, low complexity, and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. Although no active exploits have been reported, the public disclosure of the vulnerability means that threat actors could develop exploits rapidly. The affected product is a niche blood donor management system, likely deployed in healthcare environments managing sensitive donor data. The lack of available patches or vendor advisories necessitates immediate defensive measures by users. The vulnerability underscores the importance of secure coding practices, especially input validation and use of prepared statements in web applications handling critical health data.

Potential Impact

For European organizations, particularly those in the healthcare sector using the Simple Blood Donor Management System, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive donor information. Exploitation could lead to unauthorized disclosure of personal health data, manipulation of donor records, or disruption of blood donor management operations. Such incidents could result in regulatory penalties under GDPR due to data breaches, loss of public trust, and potential harm to patients relying on accurate donor information. The remote and unauthenticated nature of the exploit increases the likelihood of attacks, especially if the system is exposed to the internet or insufficiently segmented within internal networks. Additionally, the lack of patches means organizations must rely on mitigations to prevent exploitation. The impact extends beyond data loss to potential operational disruptions in critical healthcare services, which could have downstream effects on patient care and emergency response capabilities.

Mitigation Recommendations

Organizations should immediately audit their deployment of the Simple Blood Donor Management System version 1.0 to identify vulnerable instances. Since no official patches are available, the following specific mitigations are recommended: 1) Implement input validation and sanitization on the 'Name' parameter at the application level to reject or escape malicious input. 2) Refactor the code to use parameterized queries or prepared statements to prevent SQL injection. 3) Deploy a Web Application Firewall (WAF) with custom rules to detect and block SQL injection attempts targeting the /editeddonor.php endpoint. 4) Restrict network access to the application, limiting exposure to trusted internal networks or VPNs. 5) Monitor logs for suspicious SQL errors or unusual query patterns indicative of injection attempts. 6) Conduct security training for developers and administrators on secure coding and patch management. 7) Plan for migration to a patched or alternative system once available. 8) Regularly back up databases and test restoration procedures to mitigate data loss from potential attacks.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-19T10:28:03.929Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 694596660919c128848e41e0

Added to database: 12/19/2025, 6:16:06 PM

Last enriched: 12/19/2025, 6:30:20 PM

Last updated: 12/19/2025, 8:35:37 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats