# CVE-2025-58403: Reflected Cross-Site Scripting (XSS) in CGM CLININET


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-px77-24r7-j4jj

## What is CVE-2025-58403?

CVE-2025-58403 is a medium-severity vulnerability in CGM CLININET, published on 23 Oct 2026. 

### Official description

CGM CLININET is vulnerable to Reflected Cross-Site Scripting (XSS) due to improper neutralization of user-supplied data. A remote unauthenticated attacker can craft a malicious URL containing JavaScript or HTML code, which is executed in the victim's browser when the URL is visited, allowing the attacker to steal session cookies and perform actions on behalf of the victim within the application.

The vulnerability was confirmed to affect versions up to 2026.MS3 but later versions may also be vulnerable.

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

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


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

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

## Is CVE-2025-58403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58403 is a medium-severity vulnerability in CGM CLININET, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-58403 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-58403/ (Markdown: https://insights.sbomify.com/CVE-2025-58403/index.md)
```

## Sources

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

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