CWE · MITRE source
CWE-384Session Fixation
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: 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.
Last updated: 20 May 2026 01:17 UTC
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AC-12 | Session Termination | AC | Session termination after a set interval shortens the usable lifetime of a fixed session identifier, making successful exploitation of session fixation more difficult. |
IA-11 | Re-authentication | IA | Re-authentication typically forces issuance of a new session, limiting the window for exploitation of a previously fixed session identifier. |
SC-23 | Session Authenticity | SC | Enforces proper session ID generation and binding, preventing fixation of a known session token. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2018-18925 | 7.6 | 9.8 | 0.9357 | 2018-11-04 |
CVE-2022-31798 | 6.4 | 6.1 | 0.8661 | 2022-08-25 |
CVE-2017-12965 UPD | 3.3 | 9.8 | 0.2224 | 2017-08-23 |
CVE-2017-14263 UPD | 3.1 | 8.1 | 0.2442 | 2017-09-11 |
CVE-2015-4594 UPD | 2.7 | 9.8 | 0.1226 | 2017-01-10 |
CVE-2021-36394 | 2.7 | 9.8 | 0.1165 | 2023-03-06 |
CVE-2025-28242 | 2.7 | 9.8 | 0.1151 | 2025-04-18 |
CVE-2019-18418 | 2.6 | 9.8 | 0.1056 | 2019-10-24 |
CVE-2019-10008 | 2.3 | 8.8 | 0.0911 | 2019-04-24 |
CVE-2023-31498 | 2.3 | 9.8 | 0.0583 | 2023-05-11 |
CVE-2016-8638 UPD | 2.2 | 9.1 | 0.0714 | 2017-07-12 |
CVE-2015-1820 UPD | 2.2 | 9.8 | 0.0372 | 2017-08-09 |
CVE-2019-12258 | 2.2 | 7.5 | 0.1164 | 2019-08-09 |
CVE-2024-50339 | 2.2 | 5.3 | 0.1976 | 2024-12-12 |
CVE-2018-11714 | 2.1 | 9.8 | 0.0296 | 2018-06-04 |
CVE-2018-17199 | 2.1 | 7.5 | 0.1042 | 2019-01-30 |
CVE-2019-5523 | 2.1 | 9.8 | 0.0245 | 2019-04-01 |
CVE-2022-38054 | 2.1 | 9.8 | 0.0219 | 2022-09-02 |
CVE-2023-41012 | 2.1 | 9.8 | 0.0307 | 2023-09-05 |
CVE-2025-52689 | 2.1 | 9.8 | 0.0157 | 2025-07-16 |
CVE-2016-9125 UPD | 2.0 | 9.8 | 0.0107 | 2017-03-28 |
CVE-2015-1174 UPD | 2.0 | 9.8 | 0.0061 | 2017-08-02 |
CVE-2017-12868 UPD | 2.0 | 9.8 | 0.0076 | 2017-09-01 |
CVE-2017-12873 UPD | 2.0 | 9.8 | 0.0073 | 2017-09-01 |
CVE-2016-10405 UPD | 2.0 | 9.8 | 0.0056 | 2017-09-07 |