SQL InjectionWeakness · CWE-89

CVE-2025-10350

HIGH · 8.8 CVSS v4.0 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the imageserver module of CGM NETRAAD software when processing C-FIND queries (DICOM protocol). An attacker with network access to the PACS system can inject malicious SQL statements through C-FIND query parameters, potentially exfiltrating data from the underlying database that also contains CGM CLININET software data.

MitigationUpgrade CGM NETRAAD imageserver module to version 7.9.0 or later. Additionally, enforce strict network access controls on the PACS network segment to limit exposure to trusted systems only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify CGM NETRAAD imageserver installation
    Check for CGM NETRAAD software on the system by reviewing installed applications, checking for NETRAAD directories, or querying the PACS server configuration
    Affected if CGM NETRAAD with imageserver module is present on the system
  2. Determine imageserver module version
    Locate the imageserver version information through the software's built-in version display, configuration files, or PACS server administration interface
    Affected if The installed version is below 7.9.0 (the fixed version)
  3. Verify DICOM C-FIND service is enabled
    Check the PACS server configuration or service settings to confirm the DICOM C-FIND query service is active and listening for queries
    Affected if The C-FIND service is enabled and operational
  4. Assess network exposure of the PACS system
    Review network configuration, firewall rules, and access controls to determine if the PACS server with the imageserver is accessible from untrusted network segments
    Affected if The PACS system accepting C-FIND queries is reachable from networks outside trusted systems

The environment is affected if CGM NETRAAD imageserver version is below 7.9.0 and the DICOM C-FIND service is network-accessible to untrusted systems.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CGM NETRAAD imageserver module to version 7.9.0 or later. Additionally, enforce strict network access controls on the PACS network segment to limit exposure to trusted systems only.

Recommended fix Moderate confidence

CGM NETRAAD imageserver module version 7.9.0

  1. 1. Verify current installation of CGM NETRAAD with imageserver module by checking the installed version
  2. 2. If version is below 7.9.0, plan for upgrade to version 7.9.0 or later
  3. 3. Backup all database data and system configuration before performing upgrade
  4. 4. Consult CGM vendor documentation for specific upgrade procedures for NETRAAD imageserver module
  5. 5. Perform upgrade to CGM NETRAAD imageserver version 7.9.0 or newer
  6. 6. Verify successful upgrade by checking the new version number
  7. 7. Test C-FIND query functionality to confirm the SQL injection vulnerability is resolved
  8. 8. Validate database access controls are functioning properly post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data