Skip to main content
VulnerabilityPublished

CVE-2025-30037: CGM CLININET · Missing Authentication

Affects CGM CLININETSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
8.8High
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:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

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-level access restrictions: Implement firewall rules or network segmentation to restrict access to the "/int/" endpoints strictly to trusted internal services and IP ranges. 2. Deploy an authentication and authorization layer: Ensure that all internal endpoints require strong authentication mechanisms, such as mutual TLS, OAuth tokens, or API keys, to prevent unauthorized access. 3. Conduct a thorough security review of the CGM CLININET deployment to identify all exposed internal endpoints and verify their access controls. 4. Monitor network traffic and logs for unusual access patterns to the "/int/" endpoints, enabling early detection of exploitation attempts. 5. Engage with CGM for official patches or updates addressing this vulnerability and prioritize their deployment once available. 6. Implement application-layer gateways or reverse proxies that enforce authentication and restrict access to sensitive endpoints. 7. Educate IT and security teams about this vulnerability to ensure rapid response and remediation. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized access to internal paths until patches are applied.

Description

The system exposes several endpoints, typically including "/int/" in their path, that should be restricted to internal services, but are instead publicly accessible without authentication to any host able to reach the application server on port 443/tcp.

References

Community reviews

Loading reviews…