Skip to main content
VulnerabilityPublished

CVE-2024-43028: jeecg-boot · A Command Injection

Affects jeecg-bootSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 74% 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 1 Apr 2026

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.jeecg/jeecg-bootpkg:maven/org.jeecg/jeecg-bootOther threatsAffected
  • >=3.0.0 <=3.5.3
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-43028, organizations should: 1) Immediately restrict network access to the /jmreport/show endpoint using firewalls or web application firewalls (WAFs) to limit exposure to trusted users only. 2) Monitor web server and application logs for suspicious HTTP requests targeting the vulnerable endpoint, especially those containing unusual or encoded payloads. 3) Apply input validation and sanitization at the application level to prevent command injection, if source code access and modification are possible. 4) Stay alert for official patches or updates from Jeecg Boot maintainers and apply them promptly once released. 5) Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block exploitation attempts. 6) Conduct thorough security assessments and penetration testing focused on command injection vectors in the affected component. 7) Implement network segmentation to isolate critical systems and reduce the blast radius of a potential compromise. 8) Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A command injection vulnerability in the component /jmreport/show of jeecg boot v3.0.0 to v3.5.3 allows attackers to execute arbitrary code via a crafted HTTP request.

References

Community reviews

Loading reviews…