Cyber Resilience

CVE-2025-42602

Auth Bypass

Published
23 April 2025
Modified
17 June 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0040 33th percentile
Risk Priority 38 floored blend · peak EPSS

Summary

CVE-2025-42602 is a high-severity Session Fixation (CWE-384) vulnerability in Org (inferred from references). Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-12 (Session Termination) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

This vulnerability affects Meon KYC solutions and stems from improper handling of access and refresh tokens in specific API endpoints during the authentication process. The flaw is tracked under CWE-384 and CWE-613 and carries a CVSS 4.0 score of 8.2.

A remote attacker with no prior credentials can exploit the issue by intercepting and manipulating API request and response bodies, resulting in unauthorized access to other user accounts.

The Indian Computer Emergency Response Team (CERT-In) published advisory CIVN-2025-0082 on the issue.

EPSS for the CVE rose from a starting value of 0.0076 to a peak of 0.0147, indicating that exploitation interest emerged after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

This vulnerability exists in Meon KYC solutions due to improper handling of access and refresh tokens in certain API endpoints of authentication process. A remote attacker could exploit this vulnerability by intercepting and manipulating the responses through API request body…

more

leading to unauthorized access of other user accounts.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1550 Use Alternate Authentication Material Lateral Movement
Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
T1550.004 Web Session Cookie Lateral Movement
Adversaries can use stolen session cookies to authenticate to web applications and services.
T1563 Remote Service Session Hijacking Lateral Movement
Adversaries may take control of preexisting sessions with remote services to move laterally in an environment.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59841Shared CWE-384, CWE-613
CVE-2023-50270Shared CWE-384, CWE-613
CVE-2024-30262Shared CWE-384, CWE-613
CVE-2026-30224Shared CWE-384, CWE-613
CVE-2026-34454Shared CWE-384, CWE-613
CVE-2023-45718Shared CWE-384, CWE-613
CVE-2025-46344Shared CWE-613
CVE-2025-53896Shared CWE-613
CVE-2023-5889Shared CWE-613
CVE-2025-24896Shared CWE-613

Affected Assets

Org
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.4.4
  • V7.6.2

Mitigating Controls (NIST 800-53 r5) AI

AC-12 directly requires automatic session termination after a defined period, structurally preventing reuse of expired session identifiers.

Requires protection of session authenticity, which directly stops an attacker from using a stolen or fixed session identifier after authentication.

Enforces that only properly authorized (i.e., freshly authenticated) sessions can access resources, making a pre-existing fixed session ID unusable.

Forces re-authentication under defined conditions, which should result in issuance of a fresh session identifier and invalidation of any prior one.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
prevents

Credential lifecycle management directly includes enforcing session expiration to prevent reuse.

PR.AA-03 mostly match
prevents

Proper authentication processes must invalidate prior session identifiers to prevent fixation attacks.

PR.AA-05 mostly match
prevents

Authorization policy enforcement and review covers terminating stale sessions to limit access scope.

PR.AA-04 partial match
prevents

Protecting and verifying identity assertions encompasses secure handling and regeneration of session tokens.

PR.PS-01 partial match
prevents

Configuration baselines can enforce session regeneration and timeout settings that block fixation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect session-fixation issues, yet the weakness absence does not replace comprehensive testing.

degrades

Access-control policy can mandate session invalidation on re-authentication, but does not prescribe the technical mechanism.

degrades

Identity-management procedures can require new session tokens after login, yet the control is broader than session handling.

degrades

Authentication-information rules can include session-token lifecycle requirements, but the control focuses on credential management.

prevents

Secure-SDLC requirement can embed session-fixation checks, but eliminating the weakness does not satisfy the full SDLC control.

prevents

Application-security requirements can specify session handling, yet the weakness fix alone does not meet the broader requirement.

References