Skip to main content
VulnerabilityPublished

CVE-2025-30048: CGM CLININET · Missing Authentication

Affects CGM CLININETSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CGM CGM CLININETAffected
  • =0
Fixed in–

AI-suggested

  1. Immediate Network Segmentation: Restrict access to the CGM CLININET system and specifically the "serverConfig" endpoint to trusted internal networks only, using firewalls and network access controls.
  2. Implement Access Controls: Until an official patch is available, deploy web application firewalls (WAFs) or reverse proxies to enforce authentication on the vulnerable endpoint or block access entirely.
  3. Monitor and Audit: Enable detailed logging and monitoring of access to the CGM CLININET system, focusing on the "serverConfig" endpoint to detect any unauthorized access attempts.
  4. Vendor Engagement: Engage with CGM to obtain timelines for patches or updates addressing this vulnerability and apply them promptly once available.
  5. Credential Rotation: As a precaution, rotate any credentials that might have been exposed or are stored in the configuration to limit the impact of potential compromise.
  6. Incident Response Preparation: Prepare incident response plans specific to this vulnerability, including steps for containment and recovery in case of exploitation.
  7. Network Access Controls: Use VPNs or zero-trust network access solutions to limit who can reach the CGM CLININET system, reducing the risk from adjacent network attackers.
  8. Security Awareness: Educate IT and security teams about this vulnerability and the importance of monitoring and controlling access to critical healthcare systems.

Description

The "serverConfig" endpoint, which returns the module configuration including credentials, is accessible without authentication.

References

Community reviews

Loading reviews…