CVE-2024-31750: SQL Injection
Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · 19% EPSS · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 19.2% chance of exploitation in 30 days – higher than 97% 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 18 Apr 2024
Detectable: evidence found.
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
Given the absence of official patches, organizations should implement immediate compensating controls. First, apply strict input validation and sanitization on the req_id parameter at the application or web server level to block malicious SQL payloads. Employ parameterized queries or prepared statements if possible within the application codebase. Deploy a web application firewall (WAF) configured to detect and block SQL injection attempts targeting the req_id parameter and related endpoints. Conduct thorough code reviews and security testing to identify and remediate other potential injection points. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. Monitor logs and network traffic for suspicious activity indicative of SQL injection attempts. Segment the network to isolate critical systems running f-logic datacube3 and limit exposure. Prepare incident response plans specific to SQL injection attacks and ensure backups are current and tested for recovery. Engage with the vendor for updates and patches and plan for rapid deployment once available.
Description
SQL injection vulnerability in f-logic datacube3 v.1.0 allows a remote attacker to obtain sensitive information via the req_id parameter.