This page lists publicly disclosed CVE vulnerabilities affecting cgm clininet (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-58406 | The CGM CLININET application respond without essential security HTTP headers, exposing users to client‑side attacks such as clickjacking, MIME sniffing, unsafe caching, weak cross‑origin isolation, and missing transport security controls. | [email protected] | 5.3 | 0.05% | 2026-03-02 | 2026-03-09 |
| CVE-2025-58405 | The CGM CLININET application does not implement any mechanisms that prevent clickjacking attacks, neither HTTP security headers nor HTML-based frame‑busting protections were detected. As a result, an attacker can embed the application inside a maliciously crafted IFRAME and trick users into performing unintended actions, including potentially bypassing CSRF/XSRF defenses. | [email protected] | 5.3 | 0.03% | 2026-03-02 | 2026-03-09 |
| CVE-2025-58402 | The CGM CLININET application uses direct, sequential object identifiers "MessageID" without proper authorization checks. By modifying the parameter in the GET request, an attacker can access messages and attachments belonging to other users. | [email protected] | 7.1 | 0.04% | 2026-03-02 | 2026-03-09 |
| CVE-2025-30042 | The CGM CLININET system provides smart card authentication; however, authentication is conducted locally on the client device, and, in reality, only the certificate number is used for access verification. As a result, possession of the certificate number alone is sufficient for authentication, regardless of the actual presence of the smart card or ownership of the private key. | [email protected] | 9.0 | 0.01% | 2026-03-02 | 2026-03-09 |