CVE-2024-24139: Sourcecodester Login System · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jan 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
To mitigate CVE-2024-24139, organizations should immediately audit and restrict access to the affected login system, ensuring only trusted users have high privileges. Implement strong input validation and parameterized queries or prepared statements to prevent SQL Injection. Conduct thorough code reviews focusing on the 'user' parameter handling. Employ Web Application Firewalls (WAFs) with SQL Injection detection rules to block malicious payloads targeting this vulnerability. Monitor logs for unusual database queries or failed login attempts indicative of exploitation attempts. Segregate and harden database access permissions to limit damage if exploited. Until an official patch is released, consider isolating the affected system from external networks or replacing it with alternative authentication solutions. Educate developers and administrators about secure coding practices and the risks of SQL Injection. Regularly update and patch all related software components to reduce overall attack surface.
Description
Sourcecodester Login System with Email Verification 1.0 allows SQL Injection via the 'user' parameter.