CVE-2024-37699: DataLife Engine · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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 20 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
Until official patches are released, organizations should immediately audit their DataLife Engine versions and isolate vulnerable instances from public internet access where possible. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting 'dboption' parameters. Conduct thorough input validation and sanitization on all user-supplied data interacting with database queries. Monitor database logs and web server logs for anomalous queries or error messages indicative of injection attempts. Restrict database user privileges to the minimum necessary to limit potential damage. Consider deploying virtual patching techniques via WAF or reverse proxies. Engage with DataLife Engine vendors or community for updates and patches, and plan rapid deployment once available. Regularly back up databases and verify restoration procedures to mitigate data loss risks.
Description
An issue in DataLife Engine v.17.1 and before is vulnerable to SQL Injection in dboption.