CVE-2024-36611: Symfony · Incorrect Authorization
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should verify their use of Symfony, specifically the version 7.07 and the FormLoginAuthenticator component. Even though the supplier has declared the report false, it is prudent to audit authentication handling code to ensure proper validation of input fields, especially username and password. Implement additional input validation and sanitization to reject empty or malformed login requests before processing. Monitor Symfony security advisories and update to newer versions promptly if any official patches or clarifications are released. Employ web application firewalls (WAFs) to detect and block suspicious login attempts that might exploit such flaws. Conduct regular penetration testing focusing on authentication mechanisms to identify any weaknesses. Maintain robust logging and alerting on authentication failures or unusual login patterns to detect potential exploitation attempts early.
Description
In Symfony v7.07, a security vulnerability was identified in the FormLoginAuthenticator component, where it failed to adequately handle cases where the username or password field of a login request is empty. This flaw could lead to various security risks, including improper authentication logic handling or denial of service. NOTE: the Supplier has concluded that this is a false report.
References
- github.com/symfony/symfony/commit/a804ca15fcad279d7727b91d12a667fd5b925995 (opens in a new tab)
- github.com/symfony/symfony/blob/v7.0.7/src/Symfony/Component/Security/Http/Authenticator/FormLoginAuthenticator.php (opens in a new tab)
- gist.github.com/1047524396/3581425e0911b716cf8ce4fa30e41e6c (opens in a new tab)
- github.com/github/advisory-database/pull/5046 (opens in a new tab)
- github.com/symfony/symfony/issues/59077 (opens in a new tab)