Skip to main content
VulnerabilityPublished

CVE-2024-42565: ERP · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-42565, organizations should immediately conduct a thorough security review of the affected ERP system, focusing on the /index.php/basedata/contact/delete?action=delete endpoint. Specific recommendations include: 1) Implement parameterized queries or prepared statements to eliminate SQL injection risks; 2) Employ rigorous input validation and sanitization for all user-supplied data, especially URL parameters; 3) Restrict database user privileges to the minimum necessary to limit potential damage; 4) Monitor logs for suspicious SQL errors or unusual query patterns indicative of injection attempts; 5) Apply web application firewalls (WAFs) with rules targeting SQL injection signatures; 6) Segregate the ERP system network segment to reduce exposure; 7) Stay alert for vendor patches or updates addressing this vulnerability and apply them promptly once available; 8) Conduct penetration testing to verify the effectiveness of mitigations; 9) Educate development teams on secure coding practices to prevent similar issues in the future.

Description

ERP commit 44bd04 was discovered to contain a SQL injection vulnerability via the id parameter at /index.php/basedata/contact/delete?action=delete.

References

Community reviews

Loading reviews…