VulnerabilityPublished 1 Dec 2025

CVE-2025-63528: Blood Bank Management System · Cross-site Scripting

Source CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

8.5High

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

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

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

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

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

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Immediate mitigation should focus on implementing proper input validation and output encoding for the 'error' parameter in blooddinfo.php to neutralize malicious scripts. Employ context-sensitive encoding (e.g., HTML entity encoding) to ensure that injected scripts are not executed by browsers. If source code access is available, developers should adopt secure coding practices to sanitize all user inputs and consider using security libraries or frameworks that automatically handle XSS protection. In the absence of an official patch, organizations should consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting this parameter. Additionally, monitoring web server logs for suspicious requests containing script tags or unusual input patterns can help detect attempted exploitation. Restricting access to the vulnerable component to trusted users or internal networks can reduce exposure. Finally, educating users about the risks and signs of XSS attacks and ensuring browsers are updated with the latest security features can provide additional defense layers.

Description

A cross-site scripting (XSS) vulnerability exists in the Blood Bank Management System 1.0 within the blooddinfo.php component. The application fails to properly sanitize or encode user-supplied input before rendering it in response. An attacker can inject malicious JavaScript payloads into the error parameter, which is then executed in the victim's browser when the page is viewed.

Impact

For European organizations, especially those in the healthcare sector using the Blood Bank Management System 1.0, this vulnerability poses a significant risk to patient data confidentiality and system trustworthiness. Exploitation could lead to unauthorized disclosure of sensitive health information, violating GDPR and other data protection regulations, potentially resulting in legal penalties and reputational damage. The ability to execute scripts without user interaction and with low privileges means attackers could automate attacks at scale, targeting multiple users or systems. The scope change in the CVSS vector implies that the vulnerability could affect multiple components or user sessions, increasing the potential damage. Given the critical nature of blood bank systems in healthcare delivery, disruption or compromise could also impact patient care and operational continuity. European healthcare providers are thus at risk of both direct data breaches and indirect operational impacts.

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

Description

AI analysisMachine-generated, updated 8 Dec 2025, 16:04 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats