Skip to main content
VulnerabilityPublished

CVE-2024-44893: JimuReport · Improper Privilege Management

Affects JimuReportSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

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

What to do

Affected software

ProductAffectedFixed in
GitHubjeecgboot/JimuReportpkg:github/jeecgboot/JimuReportOther threatsAffected
  • =1.7.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict external network access to the /jeecg-boot/jmreport/dict/list endpoint using firewalls, web application firewalls (WAFs), or network segmentation to limit exposure. 2. Implement strict access control policies to ensure only trusted internal users can reach the vulnerable component. 3. Monitor web server logs and network traffic for unusual or suspicious GET requests targeting the vulnerable path, enabling early detection of exploitation attempts. 4. Employ intrusion detection and prevention systems (IDS/IPS) with updated signatures to identify and block exploit attempts. 5. Engage with the JimuReport vendor or community to obtain patches or updates as soon as they become available and prioritize their deployment. 6. Conduct a thorough audit of user privileges and system configurations to identify and remediate any excessive permissions that could be exploited. 7. Prepare incident response plans specifically addressing potential exploitation of this vulnerability, including containment and recovery procedures. 8. Consider deploying application-layer authentication or multi-factor authentication (MFA) around reporting tools to add an additional security layer. 9. Educate IT and security teams about this vulnerability to ensure rapid response and awareness.

Description

An issue in the component /jeecg-boot/jmreport/dict/list of JimuReport v1.7.8 allows attacker to escalate privileges via a crafted GET request.

References

Community reviews

Loading reviews…