CVE-2025-11481VulnerabilityPublished 8 Oct 2025

CVE-2025-11481: varunsardana004 Blood-Bank-And-Donation-Management-System · SQL Injection

Affects varunsardana004 Blood-Bank-And-Donation-Management-SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 8 Oct 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-26.

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

AI-suggested

Organizations should immediately implement input validation and sanitization on all user-supplied data, especially the 'fullname' parameter in /donate_blood.php, to prevent SQL injection. Employing parameterized queries or prepared statements is critical to eliminate direct SQL code injection risks. Network-level protections such as Web Application Firewalls (WAFs) should be deployed to detect and block SQL injection attempts. Regular code audits and penetration testing focused on injection flaws are recommended. Since the product uses a rolling release system with no disclosed patches, organizations should engage with the vendor for updates or consider temporary compensating controls like restricting access to the affected endpoint via network segmentation or VPNs. Logging and monitoring database queries for anomalies can help detect exploitation attempts early. Finally, ensure backups of critical data are maintained to recover from potential data integrity or availability incidents.

Description

A flaw has been found in varunsardana004 Blood-Bank-And-Donation-Management-System up to dc9e0393d826fbc85fad9755b5bc12cba1919df2. The impacted element is an unknown function of the file /donate_blood.php. Executing manipulation of the argument fullname can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.

Impact

For European organizations, particularly healthcare providers and blood donation centers using the affected system, this vulnerability poses a significant risk to sensitive personal and medical data confidentiality. Exploitation could result in unauthorized access to donor records, manipulation of blood donation data, or disruption of blood bank services, impacting patient care and operational continuity. The integrity of critical health data could be compromised, leading to erroneous medical decisions. Availability impacts, while less severe, could still disrupt donation workflows. Given the sensitive nature of healthcare data under GDPR, breaches could also result in regulatory penalties and reputational damage. The medium severity rating suggests a moderate but tangible threat that requires timely attention to prevent escalation or chaining with other vulnerabilities.

Summary

CVE-2025-11481 identifies a SQL injection vulnerability in the varunsardana004 Blood-Bank-And-Donation-Management-System, a software solution used for managing blood bank and donation operations. The vulnerability resides in the /donate_blood.php script, where the 'fullname' parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without requiring authentication or user interaction, enabling attackers to manipulate backend database queries. The product follows a rolling release model, complicating version tracking and patch management. The CVSS 4.0 score of 5.3 reflects a medium severity, indicating moderate impact on confidentiality, integrity, and availability, with low attack complexity and no privileges required. While no active exploitation has been reported, the public availability of exploit code increases the risk of attacks. The vulnerability could lead to unauthorized data disclosure, modification, or deletion, potentially disrupting blood bank operations and compromising sensitive donor and recipient information. The lack of disclosed patches necessitates immediate mitigation through secure coding practices and network defenses.

References

Community reviews

Loading reviews…