CVE-2024-37849: A SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% 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 13 Jun 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
- Immediate isolation of the affected system from the network to prevent exploitation.
- Conduct a thorough code review of process.php and all input handling routines to identify and sanitize all user inputs, especially the username parameter, using parameterized queries or prepared statements.
- Implement Web Application Firewalls (WAF) with custom rules to detect and block SQL Injection attempts targeting the vulnerable parameter.
- Monitor logs for suspicious activities related to process.php and unusual database queries.
- Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation.
- Develop and deploy patches or updates to fix the vulnerability as soon as they become available from the vendor or through internal remediation.
- Conduct penetration testing and vulnerability scanning focused on SQL Injection to identify any other potential weaknesses.
- Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.
- Prepare an incident response plan specific to SQL Injection attacks to enable rapid containment and recovery.
Description
A SQL Injection vulnerability in itsourcecode Billing System 1.0 allows a local attacker to execute arbitrary code in process.php via the username parameter.