# CVE-2025-63525: Privilege escalation in n/a

> Authenticated attackers can escalate privileges and modify data via crafted requests to delete.php in Blood Bank Management System.

- **Severity:** Critical 9.6 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-q4rm-px98-47gf

## What is CVE-2025-63525?

CVE-2025-63525 is a critical vulnerability in n/a, published on 1 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Blood Bank Management System 1.0 allowing authenticated attackers to perform actions with escalated privileges via crafted request to delete.php.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Shridharshukl Blood Bank Management System.

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

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

## Is CVE-2025-63525 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63525 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-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)
- [CVE-2025-63527](https://insights.sbomify.com/CVE-2025-63527/): Cross-site scripting in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63525 is a critical vulnerability in n/a, published on 1 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63525 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-63525/ (Markdown: https://insights.sbomify.com/CVE-2025-63525/index.md)
```

## Sources

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

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