# CVE-2025-30036: Stored XSS permitting session takeover of arbitrary user

> Stored XSS in the ward module allows attackers to hijack user sessions and escalate privileges to administrative rights.

- **Severity:** High 8.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-9vw4-5mm4-q286

## What is CVE-2025-30036?

CVE-2025-30036 is a high-severity cross-site scripting vulnerability in CGM CLININET, published on 27 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stored XSS vulnerability exists in the "Oddział" (Ward) module, in the death diagnosis description field, and allows the execution of arbitrary JavaScript code. This can lead to session hijacking of other users and potentially to privilege escalation up to full administrative rights.

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

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


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

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

## Is CVE-2025-30036 being exploited?

There is no known exploitation of CVE-2025-30036 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30036 is a high-severity cross-site scripting vulnerability in CGM CLININET, published on 27 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30036 in the wild and no public exploit code.

Affected product: CGM CLININET. 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-30036/ (Markdown: https://insights.sbomify.com/CVE-2025-30036/index.md)
```

## Sources

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

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