CVE-2024-31678: Sourcecodester Loan Management System · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Apr 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
Until an official patch is released, organizations should implement immediate mitigations including: 1) Restrict network access to the loan management system, limiting it to trusted IP addresses or internal networks only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'password' parameter in login.php. 3) Conduct thorough input validation and sanitization on all user inputs, especially the 'password' field, to neutralize malicious SQL syntax. 4) Monitor application logs and database activity for unusual queries or failed login attempts indicative of exploitation attempts. 5) Consider temporarily disabling or replacing the vulnerable login functionality if feasible. 6) Engage with the software vendor or community to obtain patches or updates as soon as they become available. 7) Educate staff on the risks and signs of exploitation to enhance incident detection and response capabilities.
Description
Sourcecodester Loan Management System v1.0 is vulnerable to SQL Injection via the "password" parameter in the "login.php" file.