slim/slim

CVE-2015-2171

CVE-2015-2171 is a high-severity code injection vulnerability in slim/slim (composer), affecting versions < 2.6.0. It is fixed in 2.6.0.

Key facts
CVSS score
N/A
High
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
slim/slim
Fixed in
2.6.0
Disclosed
2015

Summary

Middleware/SessionCookie.php in Slim before 2.6.0 allows remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via crafted session data.

Impact

What is code injection?

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Affected versions

composer

  • slim/slim (< 2.6.0)

Security releases

  • slim/slim → 2.6.0 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's Application Detection and Response identifies whether CVE-2015-2171 is reachable in your applications. Explore runtime application protection for your team.

See if CVE-2015-2171 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2015-2171 in your environment

Remediation advice

Upgrade slim/slim to 2.6.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2015-2171

What is CVE-2015-2171?

CVE-2015-2171 is a high-severity code injection vulnerability in slim/slim (composer), affecting versions < 2.6.0. It is fixed in 2.6.0. Untrusted input is evaluated as executable code within the application's runtime environment.

Which versions of slim/slim are affected by CVE-2015-2171?

slim/slim (composer) versions < 2.6.0 is affected.

Is there a fix for CVE-2015-2171?

Yes. CVE-2015-2171 is fixed in 2.6.0. Upgrade to this version or later.

Is CVE-2015-2171 exploitable, and should I be worried?

Whether CVE-2015-2171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2015-2171 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2015-2171?

Upgrade slim/slim to 2.6.0 or later.

Stop the waste.
Protect your environment with Kodem.