CVE-2024-40489: jeecg-boot · There Is an Injection
Affects jeecg-bootSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% 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 1 Apr 2026
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 |
|---|---|---|
Mavenorg.jeecg/jeecg-bootpkg:maven/org.jeecg/jeecg-bootOther 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
To mitigate CVE-2024-40489, organizations should immediately monitor for any updates or patches released by the jeecg boot maintainers and apply them as soon as they become available. In the absence of official patches, implement strict input validation and sanitization on all HTTP request parameters to block malicious payloads. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious injection attempts targeting jeecg boot endpoints. Restrict network access to the vulnerable components by limiting exposure to trusted internal networks or VPNs. Conduct thorough code reviews and penetration testing focused on injection vectors within the application. Maintain robust logging and monitoring to detect unusual activities indicative of exploitation attempts. Educate development and operations teams about secure coding practices and the risks of injection vulnerabilities. Finally, consider deploying runtime application self-protection (RASP) tools to provide an additional layer of defense against exploitation.
Description
There is an injection vulnerability in jeecg boot versions 3.0.0 to 3.5.3 due to lax character filtering, which allows attackers to execute arbitrary code on components through specially crafted HTTP requests.