CVE-2018-12071: A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode
Source CVE Database V5
Not known to be exploited : upgrade to 3.1.9 soon.
Data as of 26 Oct 2026, 12:54 UTC
Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.9
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2018
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade bcit-ci/CodeIgniter to 3.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubbcit-ci/CodeIgniterpkg:github/bcit-ci/CodeIgniterOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, European organizations should prioritize upgrading CodeIgniter to version 3.1.9 or later, where the session fixation issue has been addressed. If immediate upgrading is not feasible, organizations should implement strict session management best practices: enforce session ID regeneration upon user authentication, enable and correctly configure session.use_strict_mode in PHP to reject uninitialized session IDs, and ensure secure cookie attributes (HttpOnly, Secure, SameSite) are set to reduce session hijacking risks. Additionally, web application firewalls (WAFs) can be configured to detect and block suspicious session fixation attempts. Regular security audits and penetration testing focused on session management can help identify residual risks. Finally, educating developers about secure session handling and integrating security checks into the development lifecycle will prevent recurrence.
Description
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.