# CVE-2026-5848: jeecgboot JimuReport Data Source testConnection DriverManager.getConnection code injection

> Remote attackers can inject code via the database URL parameter in JimuReport's data source test connection feature, leading to arbitrary code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-883j-v822-6wwv

## What is CVE-2026-5848?

CVE-2026-5848 is a medium-severity code injection vulnerability in jeecgboot JimuReport, published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in jeecgboot JimuReport up to 2.3.0. The affected element is the function DriverManager.getConnection of the file /drag/onlDragDataSource/testConnection of the component Data Source Handler. Performing a manipulation of the argument dbUrl results in code injection. The attack may be initiated remotely. The exploit has been made public and could be used. The vendor confirmed the issue and will provide a fix in the upcoming release.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-5848?


## How do I fix CVE-2026-5848?

No fix has been published for CVE-2026-5848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5848 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5848 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5848 and fix it if it is affected.

What it is: CVE-2026-5848 is a medium-severity code injection vulnerability in jeecgboot JimuReport, published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5848 exists.

Affected product: jeecgboot JimuReport. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5848/ (Markdown: https://insights.sbomify.com/CVE-2026-5848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5848
- OSV: https://osv.dev/vulnerability/CVE-2026-5848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5848/
Summaries are generated and may contain mistakes; the official description above is the record.