CVE-2024-40322: JFinalCMS · SQL Injection
Affects JFinalCMSSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkakeruj/JFinalCMSpkg:github/kakeruj/JFinalCMSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Administrators should immediately audit and restrict access to the /admin/div_data/data endpoint, ensuring only trusted users have access. Implement web application firewalls (WAF) with SQL injection detection and prevention rules tailored to JFinalCMS traffic patterns. Review and refactor the CMS codebase to use parameterized queries or prepared statements instead of dynamic SQL concatenation. Conduct thorough input validation and sanitization on all user inputs, especially those reaching database queries. Monitor logs for unusual database query patterns or errors indicative of injection attempts. Until an official patch is released, consider isolating the CMS backend from untrusted networks or deploying additional network segmentation. Engage with the JFinalCMS community or vendor for updates and patches, and plan for timely application of security updates once available.
Description
An issue was discovered in JFinalCMS v.5.0.0. There is a SQL injection vulnerablity via /admin/div_data/data