CVE-2025-69602VulnerabilityPublished 28 Jan 2026Updated 29 Jan 2026

CVE-2025-69602: 66biolinks · n/a

Affects 66biolinksSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 28 Jan 2026
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 2026-10-25.

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 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
GitHubaltumcode/66biolinks`pkg:github/altumcode/66biolinks`Other threats	Affected =62.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

In the interim, organizations should implement server-side session management best practices, including enforcing session ID regeneration immediately after successful authentication to invalidate any attacker-set session IDs. Additionally, configure session cookies with the Secure and HttpOnly flags to reduce the risk of interception and cross-site scripting attacks. Employ web application firewalls (WAFs) to detect and block suspicious session-related activities. Conduct thorough security audits of session management logic and educate developers on secure session handling. Monitoring for unusual session activity and implementing multi-factor authentication can further reduce the risk of session hijacking. Finally, organizations should prepare incident response plans to quickly address any exploitation attempts.

Description

CVE-2025-69602 is a critical session fixation vulnerability in 66biolinks v62.0.0 by AltumCode. The application fails to regenerate session identifiers after user authentication, allowing attackers to hijack authenticated sessions by setting or predicting session IDs. This vulnerability has a CVSS score of 9.1, indicating high impact on confidentiality and integrity without requiring user interaction or privileges. Exploitation can lead to unauthorized access to user accounts and sensitive data. No known exploits are currently reported in the wild. European organizations using 66biolinks are at risk, especially those in countries with significant adoption of this software. Mitigation requires immediate patching or implementing session regeneration upon login to prevent session fixation attacks.

Impact

For European organizations using 66biolinks, this vulnerability can lead to severe consequences including unauthorized access to user accounts, data breaches, and potential compromise of sensitive business or customer information. Attackers exploiting this flaw can impersonate legitimate users without needing credentials, leading to data theft, fraud, or further lateral movement within the network. Given the critical CVSS score, the confidentiality and integrity of affected systems are at high risk. The availability impact is low, but the breach of trust and potential regulatory consequences under GDPR for data exposure could be substantial. Organizations in sectors such as finance, healthcare, and e-commerce, where 66biolinks might be used for link management or marketing, are particularly vulnerable. The risk is amplified in environments where session cookies are not secured with additional protections like HttpOnly or Secure flags. The absence of known exploits in the wild provides a window for proactive mitigation, but the critical nature demands urgent attention.

CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/Waqar-Arain/c8117308325a91b8f3b7829646915275 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:49 UTC

WeaknessesCWE-384

Technical details

References

Community reviews

Related threats