# CVE-2025-63529: Auth bypass in n/a

> An attacker can hijack user sessions in Blood Bank Management System by predicting session IDs, leading to unauthorized account access.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:L/PR:N/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-jfm4-64mr-fp54

## What is CVE-2025-63529?

CVE-2025-63529 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2025-63529?

It affects 1 product.


Products: Shridharshukl Blood Bank Management System.

## How do I fix CVE-2025-63529?

No fix has been published for CVE-2025-63529 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63529 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63529 exists.

## Other vulnerabilities in n/a

- [CVE-2025-63531](https://insights.sbomify.com/CVE-2025-63531/): SQL injection in n/a (critical 10.0)
- [CVE-2025-63525](https://insights.sbomify.com/CVE-2025-63525/): Privilege escalation in n/a (critical 9.6)
- [CVE-2025-63532](https://insights.sbomify.com/CVE-2025-63532/): SQL injection in n/a (critical 9.6)
- [CVE-2025-63535](https://insights.sbomify.com/CVE-2025-63535/): SQL injection in n/a (critical 9.6)
- [CVE-2025-63526](https://insights.sbomify.com/CVE-2025-63526/): Cross-site scripting in n/a (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63529 and fix it if it is affected.

What it is: CVE-2025-63529 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63529 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63529/ (Markdown: https://insights.sbomify.com/CVE-2025-63529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63529
- OSV: https://osv.dev/vulnerability/CVE-2025-63529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63529/
Summaries are generated and may contain mistakes; the official description above is the record.