How severe is CVE-2015-8125?

No CVSS score has been assigned to CVE-2015-8125 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-8125?

CVE-2015-8125 affects the following packages: symfony/symfony (Packagist), symfony/symfony (Packagist), symfony/form (Packagist), symfony/form (Packagist), symfony/form (Packagist), symfony/security-http (Packagist), symfony/security-http (Packagist), symfony/security (Packagist), and 3 more. Ecosystems affected: Packagist.

How do I fix CVE-2015-8125?

Update symfony/symfony to 2.3.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8125 is resolved across your whole dependency graph.

How do I detect CVE-2015-8125 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 CVE-2015-8125 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.

Is CVE-2015-8125 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-8125 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 CVE-2015-8125?

CVE-2015-8125 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th 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.

When was CVE-2015-8125 published, and has it been updated?

CVE-2015-8125 was published on December 7, 2015 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2015-8125: symfony CSRF — Fixed in 2.3.35

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

11 pkgs affected

🐘symfony/symfony🐘symfony/symfony🐘symfony/form🐘symfony/form🐘symfony/form🐘symfony/security-http🐘symfony/security-http🐘symfony/security+3 more

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

Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timing attack involving the (1) Symfony/Component/Security/Http/RememberMe/PersistentTokenBasedRememberMeServices or (2) Symfony/Component/Security/Http/Firewall/DigestAuthenticationListener class in the Symfony Security Component, or (3) legacy CSRF implementation from the Symfony/Component/Form/Extension/Csrf/CsrfProvider/DefaultCsrfProvider class in the Symfony Form component.

Affected Packages

11 total 11 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/symfony`	≥ 2.3.0&&< 2.3.35	2.3.35`composer require symfony/symfony:^2.3.35`
🐘Packagist	`symfony/symfony`	≥ 2.7.0&&< 2.7.7	2.7.7`composer require symfony/symfony:^2.7.7`
🐘Packagist	`symfony/form`	≥ 2.3.0&&< 2.3.35	2.3.35`composer require symfony/form:^2.3.35`
🐘Packagist	`symfony/form`	≥ 2.4.0&&< 2.6.12	2.6.12`composer require symfony/form:^2.6.12`
🐘Packagist	`symfony/form`	≥ 2.7.0&&< 2.7.7	2.7.7`composer require symfony/form:^2.7.7`
🐘Packagist	`symfony/security-http`	≥ 2.4.0&&< 2.6.12	2.6.12`composer require symfony/security-http:^2.6.12`

Affected Products

1 product · 54 configurations

Application

symfonysensiolabs

54 versions

2.3.02.3.12.3.22.3.32.3.42.3.52.3.62.3.72.3.82.3.92.3.102.3.11

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.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8125 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.

Frequently Asked Questions

Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timing attack involving the (1) Symfony/Component/Security/Http/RememberMe/PersistentTokenBasedRememberMeServices or (2) Symfony/Component/Security/Http/Firewall/DigestAuthenticationListener class in the Symfony Security Component, or (3) legacy CSRF implementation from the Symfony/Component/Form/Extension/Csrf/CsrfProvider/DefaultCsrfProvider class in the Symfony Form component.

O3 Security · Impact-Aware SCA

Is CVE-2015-8125 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2015-8125 — symfony