VulnerabilityPublished 1 Dec 2025

CVE-2025-63534: Blood-Bank-Management-System · XSS

Affects Blood-Bank-Management-SystemSource CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

8.5High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% 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

Affected software

Product	Affected	Fixed in
GitHubshridharshukl/Blood-Bank-Management-System`pkg:github/shridharshukl/Blood-Bank-Management-System`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-63534, organizations should immediately implement strict input validation and output encoding on the 'msg' and 'error' parameters within the login.php component. Employ context-aware encoding methods to neutralize any injected scripts before rendering them in the browser. Utilize security frameworks or libraries that automatically handle XSS protections. Conduct a thorough code review of the entire application to identify and remediate similar vulnerabilities. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Monitor web application logs for suspicious input patterns targeting these parameters. Restrict access to the blood bank management system to trusted networks and users, and enforce multi-factor authentication to reduce risk exposure. Regularly update and patch the system once official fixes become available. Educate users and administrators about the risks of XSS and ensure incident response plans are in place to quickly address any exploitation attempts.

Description

CVE-2025-63534 is a high-severity cross-site scripting (XSS) vulnerability in the Blood Bank Management System 1.0, specifically in the login.php component. The vulnerability arises because user inputs in the 'msg' and 'error' parameters are not properly sanitized or encoded before being rendered, allowing attackers to inject malicious JavaScript. This can lead to execution of arbitrary scripts in the victim's browser without requiring user interaction or authentication. The vulnerability has a CVSS score of 8.5, indicating a critical impact on confidentiality and a partial impact on integrity. Although no known exploits are currently in the wild, exploitation could result in session hijacking, data theft, or unauthorized actions within the application. European healthcare organizations using this system are at risk, especially those with critical blood bank infrastructure. Mitigation requires immediate input validation and output encoding, alongside monitoring and restricting access to vulnerable components.

Impact

For European organizations, particularly those in the healthcare sector managing blood bank operations, this vulnerability poses a significant risk. Exploitation could lead to unauthorized disclosure of sensitive patient and operational data, undermining confidentiality. Attackers could hijack user sessions or perform actions on behalf of legitimate users, impacting data integrity and trust in the system. Although availability is not directly affected, the resulting operational disruptions and potential regulatory non-compliance (e.g., GDPR) could have severe financial and reputational consequences. The healthcare sector is a critical infrastructure in Europe, and any compromise could affect patient care and emergency response capabilities. Additionally, the cross-site scripting vulnerability could be leveraged as a foothold for further attacks within the network, increasing the overall threat landscape. The lack of authentication or user interaction requirements lowers the barrier for attackers, increasing the likelihood of exploitation if the system remains unpatched.

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 8 Dec 2025, 17:12 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats