# CVE-2025-10350: SQL injection in CGM NETRAAD

> An attacker on the PACS network can exploit SQL injection in the imageserver module to access the database and view sensitive patient data.

- **Severity:** High 8.8 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **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:** 2 Mar 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-4648-hg34-4w7c

## What is CVE-2025-10350?

CVE-2025-10350 is a high-severity SQL injection vulnerability in CGM NETRAAD, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SQL Injection vulnerability in "imageserver" module when processing C-FIND queries in CGM NETRAAD software allows attacker connected to PACS gaining access to database, including data processed by GCM CLININET software.This issue affects CGM NETRAAD with imageserver module in versions before 7.9.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-10350 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10350 is a high-severity SQL injection vulnerability in CGM NETRAAD, published on 2 Mar 2026. 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-10350 in the wild and no public exploit code.

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

## Sources

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

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