CVE-2025-14960VulnerabilityPublished 19 Dec 2025

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

Affects code-projects Simple Blood Donor Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Simple Blood Donor Management System	Affected =1.0	Fixed in–

AI-suggested

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.

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.

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.

Summary

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.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 18:30 UTC

Technical details

References

Community reviews

Related threats