# CVE-2025-63533: Cross-site scripting in n/a

> Attackers can inject malicious JavaScript into profile fields, leading to script execution in victims' browsers and potential account takeover.

- **Severity:** High 8.5 (`CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/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:** 1 Dec 2025
- **Also known as:** GHSA-6rm6-2pr3-6wwg

## What is CVE-2025-63533?

CVE-2025-63533 is a high-severity cross-site scripting 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

A cross-site scripting (XSS) vulnerability exists in the Blood Bank Management System 1.0 within the updateprofile.php and rprofile.php components. 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 rname, remail, rpassword, rphone, rcity parameters, which are then executed in the victim's browser when the page is viewed.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Shridharshukl Blood Bank Management System.

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

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

## Is CVE-2025-63533 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63533 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-63533 and fix it if it is affected.

What it is: CVE-2025-63533 is a high-severity cross-site scripting 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-63533 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-63533/ (Markdown: https://insights.sbomify.com/CVE-2025-63533/index.md)
```

## Sources

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

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