CVE-2015-2308

CVE-2015-2308 is a medium-severity code injection vulnerability in symfony/symfony (composer), affecting versions >= 2.0.0, < 2.3.27. It is fixed in 2.3.27, 2.5.11, 2.6.6.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Symfony Vulnerable to PHP Eval Injection

Applications with ESI support (and SSI support as of Symfony 2.6) enabled and using the Symfony built-in reverse proxy (the `Symfony\Component\HttpKernel\HttpCache class) are vulnerable to PHP code injection; a malicious user can inject PHP code that will be executed by the server.

HttpCache uses eval() to execute files in its cache when they contain ESI tags (and only when ESI is enabled). The vulnerability comes from the fact that PHP allows contents of

Impact

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

symfony/symfony (>= 2.0.0, < 2.3.27) symfony/symfony (>= 2.4.0, < 2.5.11) symfony/symfony (>= 2.6.0, < 2.6.6) symfony/http-kernel (>= 2.0.0, < 2.3.27) symfony/http-kernel (>= 2.4.0, < 2.5.11) symfony/http-kernel (>= 2.6.0, < 2.6.6)

Security releases

symfony/symfony → 2.3.27 (composer) symfony/symfony → 2.5.11 (composer) symfony/symfony → 2.6.6 (composer) symfony/http-kernel → 2.3.27 (composer) symfony/http-kernel → 2.5.11 (composer) symfony/http-kernel → 2.6.6 (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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

symfony/symfony to 2.3.27 or later; symfony/symfony to 2.5.11 or later; symfony/symfony to 2.6.6 or later; symfony/http-kernel to 2.3.27 or later; symfony/http-kernel to 2.5.11 or later; symfony/http-kernel to 2.6.6 or later

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

Frequently Asked Questions

  1. What is CVE-2015-2308? CVE-2015-2308 is a medium-severity code injection vulnerability in symfony/symfony (composer), affecting versions >= 2.0.0, < 2.3.27. It is fixed in 2.3.27, 2.5.11, 2.6.6. Untrusted input is evaluated as executable code within the application's runtime environment.
  2. Which packages are affected by CVE-2015-2308?
    • symfony/symfony (composer) (versions >= 2.0.0, < 2.3.27)
    • symfony/http-kernel (composer) (versions >= 2.0.0, < 2.3.27)
  3. Is there a fix for CVE-2015-2308? Yes. CVE-2015-2308 is fixed in 2.3.27, 2.5.11, 2.6.6. Upgrade to this version or later.
  4. Is CVE-2015-2308 exploitable, and should I be worried? Whether CVE-2015-2308 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
  5. What actually determines whether CVE-2015-2308 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.
  6. How do I fix CVE-2015-2308?
    • Upgrade symfony/symfony to 2.3.27 or later
    • Upgrade symfony/symfony to 2.5.11 or later
    • Upgrade symfony/symfony to 2.6.6 or later
    • Upgrade symfony/http-kernel to 2.3.27 or later
    • Upgrade symfony/http-kernel to 2.5.11 or later
    • Upgrade symfony/http-kernel to 2.6.6 or later

Other vulnerabilities in symfony/symfony

CVE-IDSeverityPackage summary
CVE-2026-48784Mediumsymfony/routing: Symfony: UrlGenerator Dot-Segment Encoding Skips Every Other Chained `../` or `./` → Generated URL Collapses Off-Route Under RFC 3986…CVE-2026-48760Mediumsymfony/html-sanitizer: Symfony: HtmlSanitizer URL Parser Deny Gates Underinclusive: Percent-Encoded BiDi Marks and Unicode Whitespace Bypass Visual-Spoofing…CVE-2026-48747Mediumsymfony/mailomat-mailer: Symfony: Mailomat Mailer Webhook Parser Reads the HMAC Algorithm from the Request: Signature Algorithm DowngradeCVE-2026-48736Mediumsymfony/http-client: Symfony: IpUtils::PRIVATE_SUBNETS Omits IPv6 Transition Forms (6to4, NAT64, Teredo, IPv4-compatible): SSRF Bypass in…CVE-2026-48489Highsymfony/security-http: Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo