Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-44893: n/a

0
Critical
VulnerabilityCVE-2024-44893cvecve-2024-44893
Published: Tue Sep 10 2024 (09/10/2024, 00:00:00 UTC)
Source: CVE Database V5

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 08:05:04 UTC

Technical Analysis

CVE-2024-44893 is a critical security vulnerability identified in the JimuReport software, specifically within the /jeecg-boot/jmreport/dict/list component. This flaw allows an attacker to escalate privileges by sending a specially crafted GET request to the vulnerable endpoint. The vulnerability is classified under CWE-269 (Improper Privilege Management), indicating that the software fails to properly enforce access controls, enabling unauthorized privilege escalation. The CVSS v3.1 base score of 9.8 reflects the high severity, with attack vector being network-based (AV:N), requiring no authentication (PR:N), and no user interaction (UI:N). The impact affects confidentiality, integrity, and availability (C:H/I:H/A:H), meaning an attacker can fully compromise the system, access sensitive data, modify or delete data, and disrupt services. The vulnerability was reserved on August 21, 2024, and published on September 10, 2024. No patches or fixes have been released yet, and no known exploits have been detected in the wild, though the criticality suggests that exploitation attempts may emerge soon. The affected versions are not explicitly listed, but the mention of v1.7.8 implies that this or earlier versions are vulnerable. The vulnerability's exploitation requires only sending a crafted HTTP GET request, making it highly accessible to remote attackers. This flaw poses a severe risk to organizations relying on JimuReport for reporting and data management, as it could lead to full system compromise and data breaches.

Potential Impact

The impact of CVE-2024-44893 on organizations worldwide is substantial due to the critical severity and ease of exploitation. Successful exploitation allows attackers to escalate privileges without authentication, potentially gaining administrative control over affected systems. This can lead to unauthorized access to sensitive information, data manipulation or destruction, and disruption of business operations. Organizations using JimuReport for business intelligence, reporting, or data analytics could face data breaches, loss of data integrity, and service outages. The vulnerability also increases the risk of lateral movement within networks, enabling attackers to compromise additional systems. Given the lack of available patches, organizations remain exposed until mitigations or updates are applied. The threat is particularly acute for sectors with high reliance on data reporting tools, including finance, healthcare, government, and manufacturing. The potential for widespread impact is elevated by the network-exploitable nature of the vulnerability and the absence of required authentication or user interaction.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-08-21T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6ce6b7ef31ef0b56a058

Added to database: 2/25/2026, 9:43:02 PM

Last enriched: 2/26/2026, 8:05:04 AM

Last updated: 4/12/2026, 6:15:27 PM

Views: 20

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses