VulnerabilityPublished 2 Jun 2025Updated 11 Jun 2025

CVE-2025-27955: Clinical Collaboration Platform · Improper Restriction of Security Token Assignment

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected =12.2.1.5	Fixed in–

AI-suggested

Organizations should immediately audit their Clinical Collaboration Platform deployments to identify affected versions (12.2.1.5). Until a vendor patch is available, implement compensating controls such as enforcing shorter session timeouts, monitoring for unusual session reuse patterns, and requiring re-authentication for sensitive operations. Network-level protections like Web Application Firewalls (WAFs) can be tuned to detect and block suspicious token reuse attempts. Additionally, ensure secure transmission of session tokens using TLS and consider implementing multi-factor authentication (MFA) to reduce the risk of token misuse. Regularly review and revoke active sessions, especially after logout events, and educate users about the importance of logging out from shared or public devices. Engage with the vendor for timely patching and monitor threat intelligence feeds for emerging exploit reports.

Description

Clinical Collaboration Platform 12.2.1.5 has a weak logout system where the session token remains valid after logout and allows a remote attacker to obtain sensitive information and execute arbitrary code.

Impact

For European organizations, especially healthcare providers and clinical research institutions, this vulnerability could lead to unauthorized disclosure of sensitive patient data, violating GDPR and other data protection regulations. The ability to execute arbitrary code remotely could enable attackers to implant malware, disrupt clinical workflows, or manipulate medical records, potentially endangering patient safety. The persistence of session tokens post-logout undermines trust in the platform's security and could facilitate insider threats or external attackers leveraging stolen tokens. Given the critical role of clinical collaboration platforms in coordinating patient care and research, exploitation could result in operational disruptions, reputational damage, and regulatory penalties. European healthcare entities are particularly sensitive to data breaches due to stringent compliance requirements and the high value of health data on the black market.

CWE-1259Improper Restriction of Security Token Assignment (opens in a new tab)
Base weakness
The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.
Architecture and Design · Implementation
Security Token assignment review checks for design inconsistency and common weaknesses.; Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
Exploitation of Improperly Controlled Hardware Security Identifiers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/intruderlabs/cvex/tree/main/Carestream/session-token-in-url (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 05:34 UTC

WeaknessesCWE-1259

Technical details

References

Community reviews

Related threats