Skip to content
Emerging threatsCritical

CVE-2014-8686Codeigniter Vulnerability

CodeIgniter before 2.2.0 makes it easier for attackers to decode session cookies by leveraging fallback to a custom XOR-based encryption scheme when the Mcrypt extension for PHP is not available.

Published Sep 19, 2017 · Updated May 12, 2026

Key Facts

Patch immediately
  • CVE-2014-8686 is a critical-severity vulnerability (CVSS 9.8 v3) affecting Codeigniter.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 37% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Codeigniter 2.1.4.
  • Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Scores

CVSS v3

9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

37%

Higher than 98.5% of all scored CVEs

Exploit maturity

Weaponized

ATLAS score

60/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Weaponized

Public exploit code

2

Proof-of-concept links

In-the-wild evidence

1

Reports of active use

Description

CodeIgniter before 2.2.0 makes it easier for attackers to decode session cookies by leveraging fallback to a custom XOR-based encryption scheme when the Mcrypt extension for PHP is not available.

Affected Products

1 affected entries in total
ProductAffected versionsFixed in
CodeigniterCodeigniterSee advisory2.1.4

Patched Releases

Codeigniter

2.1.4

Timeline

  1. Publicly disclosed

    Sep 19, 2017

  2. Last updated

    May 12, 2026

Weakness Type

  • CWE-310

FAQ

Common Questions.

Is CVE-2014-8686 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.