Skip to main content
CVE-2024-37849VulnerabilityPublished Updated

CVE-2024-37849: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

1. Immediate isolation of the affected system from the network to prevent exploitation. 2. 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. 3. Implement Web Application Firewalls (WAF) with custom rules to detect and block SQL Injection attempts targeting the vulnerable parameter. 4. Monitor logs for suspicious activities related to process.php and unusual database queries. 5. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 6. Develop and deploy patches or updates to fix the vulnerability as soon as they become available from the vendor or through internal remediation. 7. Conduct penetration testing and vulnerability scanning focused on SQL Injection to identify any other potential weaknesses. 8. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. 9. 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.

References

Community reviews

Loading reviews…