How severe is CVE-2013-5750?

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

Which packages are affected by CVE-2013-5750?

CVE-2013-5750 affects the following packages: friendsofsymfony/user-bundle (Packagist), friendsofsymfony/user-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-5750?

Update friendsofsymfony/user-bundle to 1.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5750 is resolved across your whole dependency graph.

How do I detect CVE-2013-5750 in my Packagist dependencies?

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

How do I mitigate CVE-2013-5750 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2013-5750 actively exploited in the wild?

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

CVE-2013-5750 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th 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 CVE-2013-5750?

CVE-2013-5750 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-5750 published, and has it been updated?

CVE-2013-5750 was published on May 17, 2022 and was last updated on December 6, 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

CVE-2013-5750 — user-bundle

CVE-2013-5750 is a CWE-399 vulnerability in friendsofsymfony/user-bundle. A fix is available for friendsofsymfony/user-bundle — see the affected versions and patch details below.

FriendsOfSymfony FOSUserBundle denial of service via login form

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘friendsofsymfony/user-bundle🐘friendsofsymfony/user-bundle

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

The login form in the FriendsOfSymfony FOSUserBundle bundle before 1.3.3 for Symfony allows remote attackers to cause a denial of service (CPU consumption) via a long password that triggers an expensive hash computation, as demonstrated by a PBKDF2 computation.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`friendsofsymfony/user-bundle`	≥ 1.2.0&&< 1.2.5	1.2.5`composer require friendsofsymfony/user-bundle:^1.2.5`
🐘Packagist	`friendsofsymfony/user-bundle`	≥ 1.3.0&&< 1.3.3	1.3.3`composer require friendsofsymfony/user-bundle:^1.3.3`

Affected Products

1 product · 10 configurations

Application

fosuserbundlefriends_of_symfony_project

≤ 1.3.2

9 versions

1.0.01.1.01.2.01.2.11.2.31.2.41.2.51.3.01.3.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for friendsofsymfony/user-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update friendsofsymfony/user-bundle to 1.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5750 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-5750 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works