Skip to main content
CVE-2024-39071VulnerabilityPublished Updated

CVE-2024-39071: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 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 55% 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 9 Jul 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-25.

What to do

AI-suggested

To mitigate CVE-2024-39071 effectively, organizations should: 1) Immediately check for and apply any official patches or updates from Fujian Kelixun once available. 2) Implement strict input validation and sanitization on all parameters passed to send_event.php to prevent malicious SQL code injection. 3) Employ parameterized queries or prepared statements in the application code to eliminate direct concatenation of user input into SQL commands. 4) Restrict database user privileges to the minimum necessary, preventing the application from executing high-privilege commands. 5) Monitor database logs and web application logs for unusual query patterns or error messages indicative of injection attempts. 6) Use Web Application Firewalls (WAFs) with rules targeting SQL Injection signatures to block exploit attempts. 7) Conduct regular security assessments and code reviews focusing on input handling and database interactions. 8) Isolate critical database servers and limit network exposure to reduce attack vectors. These steps go beyond generic advice by focusing on immediate code-level and operational controls tailored to this vulnerability’s characteristics.

Description

Fujian Kelixun <=7.6.6.4391 is vulnerable to SQL Injection in send_event.php.

References

Community reviews

Loading reviews…