Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-384 (会话固定) — Vulnerability Class 160

160 vulnerabilities classified as CWE-384 (会话固定). AI Chinese analysis included.

CWE-384, Session Fixation, is an authentication weakness where an application fails to invalidate existing session identifiers upon user login. This flaw allows attackers to predict or fix a victim’s session ID before authentication occurs. Typically, an attacker tricks a user into accessing a malicious link containing the attacker’s known session ID. When the victim logs in, the server associates the authenticated session with that pre-existing ID, granting the attacker immediate access to the victim’s account without needing credentials. To prevent this, developers must generate a new, random session identifier immediately after successful authentication. Additionally, implementing secure session management practices, such as regenerating IDs after privilege changes and using secure, HTTP-only cookies, ensures that stolen session tokens remain useless to attackers, effectively mitigating the risk of session hijacking.

MITRE CWE Description
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. Such a scenario is commonly observed when: A web application authenticates a user without first invalidating the existing session, thereby continuing to use the session already associated with the user. An attacker is able to force a known session identifier on a user so that, once the user authenticates, the attacker has access to the authenticated session. The application or container uses predictable session identifiers. In the generic exploit of session fixation vulnerabilities, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to associate, and possibly authenticate, against the server using that session identifier, giving the attacker access to the user's account through the active session.
Common Consequences (1)
Access ControlGain Privileges or Assume Identity
Mitigations (3)
Architecture and DesignInvalidate any existing session identifiers prior to authorizing a new user session.
Architecture and DesignFor 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. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
OperationUse 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 [REF-1481].
Effectiveness: Moderate
Examples (2)
The following example shows a snippet of code from a J2EE web application where the application authenticates users with LoginContext.login() without first calling HttpSession.invalidate().
private void auth(LoginContext lc, HttpSession session) throws LoginException { ... lc.login(); ... }
Bad · Java
The following example shows a snippet of code from a J2EE web application where the application authenticates users with a direct post to the <code>j_security_check</code>, which typically does not invalidate the existing session before processing the login request.
<form method="POST" action="j_security_check"> <input type="text" name="j_username"> <input type="text" name="j_password"> </form>
Bad · HTML
CVE IDTitleCVSSSeverityPublished
CVE-2026-14609 SourceCodester CET Automated Grading System with AI Predictive Analytics session fixiation — CET Automated Grading System with AI Predictive Analytics 5.6 Medium2026-07-03
CVE-2026-13707 Session fixation attacks on improperly configured OAuth 1.0a tools — OAuth--2026-07-01
CVE-2026-56224 Capgo - Login CSRF and Session Fixation via URL Query Parameters — Capgo 5.4 Medium2026-06-30
CVE-2026-35095 Session fixation in KTM System e-BOK — e-BOK--2026-06-30
CVE-2026-40082 Cacti: Session Fixation via missing session_regenerate_id() after login — cacti 5.4 Medium2026-06-25
CVE-2026-56425 MISP AAD authentication plugin - Improper OAuth State Handling, Missing Session Rotation, Insecure Redirect URI Validation, and Log Injection — misp--2026-06-22
CVE-2026-12581 Digiwin|EasyFlow .NET - Session Fixation — EasyFlow .NET 7.5 High2026-06-22
CVE-2009-10007 Catalyst::Plugin::Authentication versions before 0.10_027 for Perl is susceptible to session fixation attacks — Catalyst::Plugin::Authentication--2026-06-09
CVE-2026-41839 Spring Framework Escalation via Session Fixation in WebFlux — Spring Framework 4.2 Medium2026-06-09
CVE-2026-11335 tittuvarghese CollegeManagementSystem login-form.php session_start session fixiation — CollegeManagementSystem 6.3 Medium2026-06-05
CVE-2026-33384 Session Fixation in QuickCMS — QuickCMS--2026-05-29
CVE-2026-48545 Gradio < 6.15.0 Cookie Injection via Shared Proxy Client — gradio 6.8 Medium2026-05-27
CVE-2026-43827 Apache Shiro: Session fixation: new session is not created after login by default — Apache Shiro--2026-05-25
CVE-2026-41613 Visual Studio Code Elevation of Privilege Vulnerability — Visual Studio Code 8.8 High2026-05-12
CVE-2026-30808 Session Fixation in Authentication leads to Session Hijacking — Pandora FMS--2026-05-12
CVE-2025-46605 Dell PowerProtect Data Domain(Dell PowerProtect DD) 安全漏洞 — PowerProtect Data Domain 6.2 Medium2026-04-17
CVE-2026-31940 Session Fixation in Chamilo LMS — chamilo-lms 7.5 High2026-04-10
CVE-2026-33946 MCP Ruby SDK: Insufficient Session Binding Allows SSE Stream Hijacking via Session ID Replay — ruby-sdk 8.2 -2026-03-27
CVE-2026-33757 OpenBao lacks user confirmation for OIDC direct callback mode — openbao 9.6 Critical2026-03-27
CVE-2026-25101 Session Fixation in Bludit — Bludit 9.1 -2026-03-27
CVE-2025-55266 HCL Aftermarket DPC is affected by Session Fixation — Aftermarket DPC 5.9 Medium2026-03-26
CVE-2026-33492 AVideo has Session Fixation via GET PHPSESSID Parameter With Disabled Login Session Regeneration — AVideo 7.3 High2026-03-23
CVE-2026-30224 OliveTin: Session Fixation - Logout Fails to Invalidate Server-Side Session — OliveTin 5.4 Medium2026-03-06
CVE-2026-24352 Session Fixation in PluXml CMS — PluXml CMS 8.2 -2026-02-27
CVE-2026-2177 SourceCodester Prison Management System Login session fixiation — Prison Management System 7.3 High2026-02-08
CVE-2026-23796 Session Fixation in Quick.Cart — Quick.Cart 8.1AIHighAI2026-02-05
CVE-2026-23624 GLPI is vulnerable to session stealing on externally authenticated user change — glpi 4.3 Medium2026-02-04
CVE-2025-7014 Session Hijacking in QRMenumPro's Menu Panel — Menu Panel 5.7 Medium2026-01-29
CVE-2025-7015 Session Hijacking in Akinsoft's QR Menu — QR Menu 5.7 Medium2026-01-29
CVE-2025-68139 In EVerest, by default, the EV is responsible for closing the connection if the module encounters an error during request processing — everest-core 4.3 Medium2026-01-21

Vulnerabilities classified as CWE-384 (会话固定) represent 160 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.