How severe is GHSA-5c58-w9xc-qcj9?

No CVSS score has been assigned to GHSA-5c58-w9xc-qcj9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5c58-w9xc-qcj9?

GHSA-5c58-w9xc-qcj9 affects the following packages: symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/http-kernel (Packagist), symfony/http-kernel (Packagist), symfony/http-kernel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5c58-w9xc-qcj9?

Update symfony/symfony to 2.3.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5c58-w9xc-qcj9 is resolved across your whole dependency graph.

How do I detect GHSA-5c58-w9xc-qcj9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5c58-w9xc-qcj9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5c58-w9xc-qcj9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5c58-w9xc-qcj9 can be triaged on real exposure rather than presence alone.

Is GHSA-5c58-w9xc-qcj9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5c58-w9xc-qcj9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5c58-w9xc-qcj9?

GHSA-5c58-w9xc-qcj9 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5c58-w9xc-qcj9?

GHSA-5c58-w9xc-qcj9 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-5c58-w9xc-qcj9 published, and has it been updated?

GHSA-5c58-w9xc-qcj9 was published on May 17, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-5c58-w9xc-qcj9 — symfony/symfony

Fix: symfony/symfony#14167

GHSA-5c58-w9xc-qcj9 is a Code Injection vulnerability in symfony/symfony. A fix is available for symfony/symfony — see the affected versions and patch details below.

Symfony Vulnerable to PHP Eval Injection

Also known asCVE-2015-2308

Published

May 17, 2022

Updated

Dec 8, 2024

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected

🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/http-kernel🐘symfony/http-kernel🐘symfony/http-kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 <script language="php"> tags to be executed (and this kind of PHP tags is always available regardless of the configuration), but there were not escaped before the evaluation.

A possible exploit comes from websites also vulnerable to Cross-Site Scripting as an attacker can successfully conduct a PHP code injection attack by passing such a tag in a user submitted variable (for which proper output escaping was not applied).

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/symfony`	≥ 2.0.0&&< 2.3.27	2.3.27`composer require symfony/symfony:^2.3.27`
🐘Packagist	`symfony/symfony`	≥ 2.4.0&&< 2.5.11	2.5.11`composer require symfony/symfony:^2.5.11`
🐘Packagist	`symfony/symfony`	≥ 2.6.0&&< 2.6.6	2.6.6`composer require symfony/symfony:^2.6.6`
🐘Packagist	`symfony/http-kernel`	≥ 2.0.0&&< 2.3.27	2.3.27`composer require symfony/http-kernel:^2.3.27`
🐘Packagist	`symfony/http-kernel`	≥ 2.4.0&&< 2.5.11	2.5.11`composer require symfony/http-kernel:^2.5.11`
🐘Packagist	`symfony/http-kernel`	≥ 2.6.0&&< 2.6.6	2.6.6`composer require symfony/http-kernel:^2.6.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/symfony to 2.3.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5c58-w9xc-qcj9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5c58-w9xc-qcj9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5c58-w9xc-qcj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 <script language="php"> tags to be executed (and this kind of PHP tags is always available regardless of the configuration), but there were

O3 Security · Impact-Aware SCA

Is GHSA-5c58-w9xc-qcj9 in your dependencies?

O3 Security finds GHSA-5c58-w9xc-qcj9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works