CVE-2024-0476VulnerabilityPublished 13 Jan 2024Updated 3 Jun 2025

CVE-2024-0476: Blood Bank & Donor Management · Cross Site Scripting

Affects Blood Bank & Donor ManagementSource CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

2.4Low

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

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2024
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
n/a Blood Bank & Donor Management	Affected =1.0	Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Conduct a thorough code review of the request-received-bydonar.php file and other input handling components to identify and sanitize all user inputs properly, employing context-appropriate output encoding to prevent script injection. 2) Enforce strict access controls to limit high-privilege user accounts and monitor their activity for unusual behavior. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the application. 4) Educate users, especially administrators and staff with elevated privileges, about the risks of interacting with untrusted inputs and phishing attempts. 5) If possible, isolate the Blood Bank & Donor Management system within a segmented network zone to reduce exposure. 6) Monitor vendor communications for patches or updates addressing this vulnerability and apply them promptly once available. 7) Consider deploying Web Application Firewalls (WAF) with rules tuned to detect and block XSS payloads targeting this application.

Description

A vulnerability, which was classified as problematic, was found in Blood Bank & Donor Management 1.0. This affects an unknown part of the file request-received-bydonar.php. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250581 was assigned to this vulnerability.

Impact

For European organizations using the Blood Bank & Donor Management software version 1.0, this vulnerability poses a risk primarily to data integrity within the application interface. Although the CVSS score is low, the presence of XSS in healthcare-related software is concerning because it could be leveraged to perform targeted attacks on healthcare staff or donors by injecting malicious scripts that alter displayed information or steal session tokens if combined with other vulnerabilities. This could lead to misinformation, unauthorized actions within the system, or phishing attacks targeting users with elevated privileges. Given the sensitive nature of blood bank data, even minor integrity compromises can undermine trust and operational effectiveness. However, since exploitation requires high privileges and user interaction, the risk to organizations with strong access controls and user awareness training is mitigated. The lack of known exploits in the wild further reduces immediate risk but does not eliminate the need for vigilance.

Summary

CVE-2024-0476 is a cross-site scripting (XSS) vulnerability identified in version 1.0 of the Blood Bank & Donor Management software, specifically within the file request-received-bydonar.php. The vulnerability is classified under CWE-79, which pertains to improper neutralization of input leading to XSS attacks. This flaw allows an attacker to inject malicious scripts into the web application, which can then be executed in the context of a victim's browser session. The vulnerability can be exploited remotely, but requires that the attacker have high privileges (PR:H) and that the user interacts with the malicious input (UI:R). The CVSS v3.1 base score is 2.4, indicating a low severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), but the impact is limited to integrity (I:L) with no confidentiality or availability impact. No public exploits are currently known in the wild, and no patches have been published yet. The vulnerability arises from insufficient input validation or output encoding in the affected PHP file, allowing script injection that could manipulate or alter data displayed to users or administrators.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 14:58 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats