Skip to content
Fencer Intel
medium 4.3

CVE-2015-4050 json

Symfony Incorrect Access Control

published 2015-06-02 11 y ago modified 2026-06-17 4 mo ago also GHSA-qmqw-mpqp-mr54 , EUVD-2022-5002

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.2%
EPSS 8.2% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known, plus a Nuclei check

Summary

FragmentListener in the HttpKernel component in Symfony 2.3.19 through 2.3.28, 2.4.9 through 2.4.10, 2.5.4 through 2.5.11, and 2.6.0 through 2.6.7, when ESI or SSI support enabled, does not check if the _controller attribute is set, which allows remote attackers to bypass URL signing and security rules by including (1) no hash or (2) an invalid hash in a request to /_fragment.

Patch / fix

  • packagist symfony/http-kernel 2.3.29, 2.5.12, 2.6.8
  • packagist symfony/symfony 2.3.29, 2.5.12, 2.6.8
  • symfony Debian 14, Debian 13, Debian 12 2.7.0~beta2+dfsg-2

debian advisories DEBIAN-CVE-2015-4050

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-4050 updated cvss 6.4

php-symfony: ESI unauthorized access

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

8.21% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
packagist symfony/http-kernel
>=2.3.19, <2.3.29
>=2.5.4, <2.5.12
>=2.6.0, <2.6.8
>=2.4.9, <=2.4.10
2.3.29
2.5.12
2.6.8
packagist symfony/symfony
>=2.3.19, <2.3.29
>=2.4.9, <=2.4.10
>=2.5.4, <2.5.12
>=2.6.0, <2.6.8
2.3.29
2.5.12
2.6.8

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.