MEDIUMCVE-2026-5848CVSS 4.7

CVE-2026-5848: Code Injection in JimuReport 2.0.0-2.3.0

Platform

java

Component

jeecgboot-jimureport

Fixed in

2.0.1

2.1.1

2.2.1

2.3.1

AI Confidence: highNVDEPSS 0.1%Reviewed: May 2026

CVE-2026-5848 describes a code injection vulnerability discovered in JimuReport, a reporting tool, affecting versions 2.0.0 through 2.3.0. An attacker can exploit this flaw by manipulating the dbUrl parameter within the /drag/onlDragDataSource/testConnection file, potentially leading to remote code execution. The vendor has acknowledged the issue and plans to release a patch in a future update. Exploitation is currently possible due to the public availability of a proof-of-concept.

Java / Maven

Detect this CVE in your project

Upload your pom.xml file and we'll tell you instantly if you're affected.

Upload pom.xmlSupported formats: pom.xml · build.gradle

Impact and Attack Scenarios

Successful exploitation of CVE-2026-5848 allows an attacker to inject and execute arbitrary code on the JimuReport server. This could lead to complete system compromise, including data exfiltration, modification, or deletion. The attacker could potentially gain control of the underlying database, access sensitive reports, and pivot to other systems on the network. Given the remote nature of the vulnerability and the availability of a public exploit, the blast radius is significant, potentially impacting all systems running vulnerable versions of JimuReport. The ability to inject code via a database connection parameter is a concerning pattern, similar to vulnerabilities that have previously allowed attackers to bypass authentication and gain privileged access.

Exploitation Context

CVE-2026-5848 is currently considered a high-priority vulnerability due to the public availability of a proof-of-concept exploit. While it is not yet listed on CISA KEV, its ease of exploitation and potential impact suggest it could be added in the future. The vulnerability was publicly disclosed on 2026-04-09, indicating a relatively short timeframe between discovery and public awareness. Active exploitation is likely, and organizations should prioritize remediation.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

EPSS

0.07% (21% percentile)

CISA SSVC

Exploitationpoc
Automatableno
Technical Impactpartial

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C4.7MEDIUMAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredHighAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityLowRisk of sensitive data exposureIntegrityLowRisk of unauthorized data modificationAvailabilityLowRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
High — admin or privileged account required to exploit.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
Low — partial or indirect data access. Attacker gains limited information.
Integrity
Low — attacker can modify some data with limited scope or impact.
Availability
Low — partial or intermittent denial of service. Attacker can degrade performance.

Affected Software

Componentjeecgboot-jimureport
Vendorjeecgboot
Affected rangeFixed in
2.0 – 2.02.0.1
2.1 – 2.12.1.1
2.2 – 2.22.2.1
2.3.0 – 2.3.02.3.1

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published
  3. EPSS updated
Unpatched — 45 days since disclosure

Mitigation and Workarounds

The primary mitigation for CVE-2026-5848 is to upgrade to the patched version of JimuReport as soon as it becomes available. Since a fixed version is not yet released, immediate workarounds are limited. Consider implementing strict input validation on the dbUrl parameter within the /drag/onlDragDataSource/testConnection file to prevent malicious input. Web application firewalls (WAFs) configured to detect and block code injection attempts targeting database connection parameters could provide an additional layer of defense. Monitor JimuReport logs for suspicious activity, particularly connection attempts with unusual or malformed dbUrl values. Review and restrict network access to the JimuReport server to minimize the potential attack surface.

How to fix

Update to the patched version provided by the vendor in a future release. Verify the official jeecgboot documentation for more details on the update and any temporary mitigation measures if available. Rigorously validate and sanitize all user inputs, especially the database URL, to prevent code injection.

CVE Security Newsletter

Vulnerability analysis and critical alerts directly to your inbox.

Frequently asked questions

What is CVE-2026-5848 — Code Injection in JimuReport?

CVE-2026-5848 is a code injection vulnerability affecting JimuReport versions 2.0.0 through 2.3.0. It allows attackers to execute arbitrary code by manipulating the dbUrl parameter, potentially leading to system compromise.

Am I affected by CVE-2026-5848 in JimuReport?

If you are running JimuReport versions 2.0.0 to 2.3.0, you are potentially affected by this vulnerability. Monitor for updates and apply the fix as soon as it's available.

How do I fix CVE-2026-5848 in JimuReport?

The vendor is preparing a patch. Until then, implement strict input validation on the dbUrl parameter and consider WAF rules to mitigate the risk. Upgrade immediately upon patch release.

Is CVE-2026-5848 being actively exploited?

Due to the public availability of a proof-of-concept, active exploitation is likely. Organizations should prioritize remediation to prevent potential attacks.

Where can I find the official JimuReport advisory for CVE-2026-5848?

Refer to the JimuReport vendor website and security advisories for the latest information and official patch release announcements.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.