Skip to content
Fencer Intel
low 3.1

CVE-2015-8124 json

Symfony Session Fixation Vulnerability

published 2015-12-07 10 y ago modified 2026-06-17 4 mo ago also GHSA-j5jh-hpr4-h332 , EUVD-2022-4284

cvss
3.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

Session fixation vulnerability in the "Remember Me" login feature in Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 allows remote attackers to hijack web sessions via a session id.

Patch / fix

  • packagist symfony/symfony 2.3.35, 2.6.12, 2.7.7
  • packagist symfony/security-http 2.6.12, 2.7.7
  • packagist symfony/security 2.3.35, 2.6.12, 2.7.7
  • symfony Debian 14, Debian 13, Debian 12 2.7.7+dfsg-1

debian advisories DEBIAN-CVE-2015-8124

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-8124 updated cvss 5.8

php-symfony: Session fixation and remote timing attack vulnerabilities

  • 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

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

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist symfony/symfony
>=2.3.0, <2.3.35
>=2.4.0, <2.6.12
>=2.7.0, <2.7.7
2.3.35
2.6.12
2.7.7
packagist symfony/security-http
>=2.4.0, <2.6.12
>=2.7.0, <2.7.7
2.6.12
2.7.7
packagist symfony/security
>=2.3.0, <2.3.35
>=2.4.0, <2.6.12
>=2.7.0, <2.7.7
2.3.35
2.6.12
2.7.7

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.