CVE-2025-63529VulnerabilityPublished 1 Dec 2025

CVE-2025-63529: Blood-Bank-Management-System · n/a

Affects Blood-Bank-Management-SystemSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.1Medium

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

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

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

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

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: 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 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.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.

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 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

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

1. Implement session ID regeneration immediately upon successful user authentication to prevent session fixation. 2. Enforce secure cookie attributes such as HttpOnly, Secure, and SameSite to protect session cookies from interception and cross-site attacks. 3. Conduct thorough code reviews and security testing focusing on session management logic within login.php and related components. 4. Educate users and administrators about the risks of session fixation and encourage vigilance against phishing or social engineering attempts that could facilitate session fixation. 5. Monitor application logs for unusual session activity or multiple logins from the same session ID. 6. If possible, deploy Web Application Firewalls (WAFs) with rules to detect and block session fixation attempts. 7. Coordinate with the vendor or development team to release and apply patches addressing this vulnerability promptly. 8. Review and update session timeout policies to limit the window of opportunity for attackers.

Description

A session fixation vulnerability exists in Blood Bank Management System 1.0 in login.php that allows an attacker to set or predict a user's session identifier prior to authentication. When the victim logs in, the application continues to use the attacker-supplied session ID rather than generating a new one, enabling the attacker to hijack the authenticated session and gain unauthorized access to the victim's account.

Impact

For European organizations, particularly healthcare providers and blood banks using the Blood Bank Management System 1.0, this vulnerability could lead to unauthorized access to sensitive patient and donor data. Attackers exploiting this flaw can hijack authenticated sessions, potentially manipulating or stealing confidential information, which may violate GDPR and other data protection regulations. The breach of patient data confidentiality could result in legal penalties, reputational damage, and loss of trust. Additionally, unauthorized access could disrupt blood bank operations by altering records, affecting blood supply management. The medium severity score reflects that while the attack requires user interaction, the ease of exploitation and the critical nature of healthcare data elevate the risk. Given the sensitive nature of healthcare systems, even medium severity vulnerabilities warrant urgent attention.

CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (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, 16:05 UTC

WeaknessesCWE-384

Technical details

References

Community reviews

Related threats