CVE-2026-2060VulnerabilityPublished 6 Feb 2026Updated 23 Feb 2026

CVE-2026-2060: 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 31% 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 6 Feb 2026
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-projectsSimple Blood Donor Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately implement input validation and sanitization on the 'ID' parameter in the /simpleblooddonor/editcampaignform.php file. Employing parameterized queries or prepared statements is critical to prevent SQL Injection. Restrict database user permissions to the minimum necessary to limit the impact of any potential exploitation. Network-level protections such as web application firewalls (WAFs) can help detect and block SQL Injection attempts. Regularly audit and monitor database logs for suspicious activities. If possible, isolate the affected system from direct internet exposure and apply network segmentation to reduce attack surface. Organizations should also seek or develop patches from the vendor or community and apply them promptly once available. Conduct security awareness training for developers to prevent similar vulnerabilities in future code. Finally, maintain up-to-date backups to enable recovery in case of data corruption or loss.

Description

A vulnerability was found in code-projects Simple Blood Donor Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /simpleblooddonor/editcampaignform.php. Performing a manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been made public and could be used.

Impact

The SQL Injection vulnerability can have severe consequences for organizations using the affected Simple Blood Donor Management System. Attackers exploiting this flaw can gain unauthorized access to sensitive donor information, including personal and medical data, violating confidentiality. They may also alter or delete data, undermining data integrity and potentially disrupting blood donation campaigns and healthcare services, thus affecting availability. Such data breaches can lead to regulatory penalties, loss of trust, and operational downtime. Given the healthcare context, the impact extends beyond IT systems to patient safety and public health. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially if the system is internet-facing. Organizations with inadequate network segmentation or monitoring are particularly vulnerable to exploitation and subsequent lateral movement within their networks.

Summary

CVE-2026-2060 is a SQL Injection vulnerability identified in the Simple Blood Donor Management System version 1.0, specifically in the /simpleblooddonor/editcampaignform.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, which is directly used in SQL queries without adequate validation or parameterization. This allows remote attackers to inject malicious SQL code by manipulating the 'ID' argument, potentially leading to unauthorized data retrieval, modification, or deletion within the backend database. The vulnerability requires no authentication or user interaction, making it exploitable remotely over the network. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation and potential impact on confidentiality, integrity, and availability, though the scope is limited to this specific application. No patches or fixes have been officially released yet, and while the exploit code is publicly available, no confirmed active exploitation has been reported. The vulnerability poses a significant risk to organizations relying on this system for managing sensitive blood donor data, as attackers could compromise personal and medical information or disrupt critical healthcare operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:08 UTC

Technical details

References

Community reviews

Related threats