VulnerabilityPublished 27 Oct 2025Updated 28 Oct 2025

CVE-2025-27223: TRUfusion Enterprise · Sensitive Cookie Without 'HttpOnly' Flag

Source CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 2.2% chance of exploitation in 30 days – higher than 82% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 27 Oct 2025
Detectable: evidence found.
nuclei template: TRUfusion Enterprise <= 7.10.4.0 - Authentication Bypass
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

AI-suggested

Organizations should immediately audit their TRUfusion Enterprise deployments to identify affected versions. Since no official patches are available, temporary mitigations include disabling or restricting access to vulnerable endpoints like /trufusionPortal/getProjectList via network controls or web application firewalls. Implement multi-factor authentication (MFA) on all sensitive endpoints to reduce reliance on cookie-based authentication. Review and update the cookie encryption mechanism to replace the static key with dynamic, per-session keys or use established secure token standards such as JWT with proper signing and expiration. Monitor logs for unusual access patterns indicative of forged cookie usage. Engage with the vendor for timely patch releases and apply updates as soon as they become available. Additionally, conduct security awareness training for administrators to recognize and respond to potential exploitation attempts.

Description

TRUfusion Enterprise through 7.10.4.0 exposes the encrypted COOKIEID as an authentication mechanism for some endpoints such as /trufusionPortal/getProjectList. However, the application uses a static key to create the encrypted cookie, ultimately allowing anyone to forge cookies and gain access to sensitive internal information.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive internal data managed through TRUfusion Enterprise. Attackers can remotely forge authentication cookies and access project lists or other sensitive information without detection. This could lead to data leaks, exposure of proprietary or personal data, and potential compliance violations under GDPR due to unauthorized data access. While integrity and availability are not directly impacted, the breach of confidentiality alone can damage organizational reputation, result in financial penalties, and facilitate further attacks leveraging the exposed information. Organizations in sectors such as manufacturing, engineering, or project management that rely on TRUfusion Enterprise for internal collaboration are particularly vulnerable. The absence of required privileges or user interaction lowers the barrier for exploitation, increasing the likelihood of attacks if the vulnerability is not remediated promptly.

CWE-1004Sensitive Cookie Without 'HttpOnly' Flag (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.
Implementation
Leverage the HttpOnly flag when setting a sensitive cookie in a response.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.2 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 16:54 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-1004

Technical details

References

Community reviews

Related threats