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: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 10 mapping(s) from 4 framework(s): CAPEC 6 (full) · ASVS 5.0 2 (mostly) · OWASP-Web 1 (full) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
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. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2015-4594 | 7.0 | 9.8 | 0.0624 | 2017-01-10 |
CVE-2016-9125 | 7.0 | 9.8 | 0.0266 | 2017-03-28 |
CVE-2016-8638 | 7.0 | 9.1 | 0.0212 | 2017-07-12 |
CVE-2015-1174 | 7.0 | 9.8 | 0.0291 | 2017-08-02 |
CVE-2015-1820 | 7.0 | 9.8 | 0.0435 | 2017-08-09 |
CVE-2017-12965 | 7.0 | 9.8 | 0.1567 | 2017-08-23 |
CVE-2017-12868 | 7.0 | 9.8 | 0.0213 | 2017-09-01 |
CVE-2017-12873 | 7.0 | 9.8 | 0.0166 | 2017-09-01 |
CVE-2016-10405 | 7.0 | 9.8 | 0.0193 | 2017-09-07 |
CVE-2017-15304 | 7.0 | 9.8 | 0.0120 | 2017-10-15 |
CVE-2018-6959 | 7.0 | 9.8 | 0.0207 | 2018-04-13 |
CVE-2018-11714 | 7.0 | 9.8 | 0.3652 | 2018-06-04 |
CVE-2018-12071 | 7.0 | 9.8 | 0.0125 | 2018-06-17 |
CVE-2016-6545 | 7.0 | 9.8 | 0.0306 | 2018-07-13 |
CVE-2018-18925 | 7.0 | 9.8 | 0.3188 | 2018-11-04 |
CVE-2018-18926 | 7.0 | 9.8 | 0.0304 | 2018-11-04 |
CVE-2019-7747 | 7.0 | 9.6 | 0.0140 | 2019-02-11 |
CVE-2019-5523 | 7.0 | 9.8 | 0.0326 | 2019-04-01 |
CVE-2019-18418 | 7.0 | 9.8 | 0.0400 | 2019-10-24 |
CVE-2019-10158 | 7.0 | 9.8 | 0.0196 | 2020-01-02 |
CVE-2020-8990 | 7.0 | 9.1 | 0.0100 | 2020-02-20 |
CVE-2020-9370 | 7.0 | 9.1 | 0.0120 | 2020-03-05 |
CVE-2020-5543 | 7.0 | 9.8 | 0.0215 | 2020-03-16 |
CVE-2020-11729 | 7.0 | 9.8 | 0.0188 | 2020-04-15 |
CVE-2020-12258 | 7.0 | 9.1 | 0.0171 | 2020-05-18 |