Cgm Clininet

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.

Published: 2026-03-02T11:16:56.975Z
Updated: 2026-03-02T12:21:46.406Z

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.

Published: 2026-03-02T11:16:45.223Z
Updated: 2026-03-02T12:27:59.659Z

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.

Published: 2026-03-02T11:16:31.420Z
Updated: 2026-03-02T12:39:17.339Z

An insufficiently secured internal function allows session generation for arbitrary users. The decodeParam function checks the JWT but does not verify which signing algorithm was used. As a result, an attacker can use the "ex:action" parameter in the VerifyUserByThrustedService function to generate a session for any user.

Published: 2025-08-27T10:25:20.090Z
Updated: 2025-08-27T13:25:58.795Z

The configuration file containing database logins and passwords is readable by any local user.

Published: 2025-08-27T10:25:02.678Z
Updated: 2025-08-27T13:28:38.439Z