CVE-2021-3311 json
October CMS Session ID not invalidated after logout
published 2021-02-05 5 y ago modified 2026-06-17 4 mo ago also GHSA-7ggw-h8pp-r95r , EUVD-2021-0537
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
An issue was discovered in October through build 471. It reactivates an old session ID (which had been invalid after a logout) once a new login occurs. NOTE: this violates the intended Auth/Manager.php authentication behavior but, admittedly, is only relevant if an old session ID is known to an attacker.
Patch / fix
Exploit prediction
2.96% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- anisiosantos.me https://anisiosantos.me/october-cms-token-reactivation referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | october/rain | <1.0.472 >=1.1.0, <1.1.2 |
1.0.472 1.1.2 |
Classification
- Weakness
-
- CWE-613 DEPRECATED: Insufficient Session Expiration
References
-
github.com
/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024
web, patch, third-party-advisory
-
anisiosantos.me
/october-cms-token-reactivation
web, exploit, third-party-advisory
-
octobercms.com
/forum/chan/announcements
web, vendor-advisory
-
github.com
/octobercms/october/security/advisories/GHSA-7ggw-h8pp-r95r
web
-
nvd.nist.gov
/vuln/detail/CVE-2021-3311
advisory
-
packagist.org
/packages/october/rain
web
-
cve.circl.lu
/cve/CVE-2021-3311
web
Sources
- CVE List CVE-2021-3311
- GitHub Advisory GHSA-7ggw-h8pp-r95r
- NVD CVE-2021-3311
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.