Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
CVE-2025-66913: JimuReport versions up to 2.1.3 allow malicious database connections
CVE-2025-66913 · published 10 months ago
Summary
A weakness in JimuReport versions 2.1.3 and earlier allows hackers to execute unauthorized code on the server when a malicious database connection is made. This could lead to data theft or system compromise. Update to version 2.1.4 or later to address this risk.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| jeecg | jimureport |
<= 2.1.3 cpe:2.3:a:jeecg:jimureport:*:*:*:*:*:*:*:* |
Original advisory text
JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC URLs. The application passes the attacker-supplied JDBC URL directly to the H2 driver, a...
JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC URLs. The application passes the attacker-supplied JDBC URL directly to the H2 driver, allowing the use of certain directives to execute arbitrary Java code. A different vulnerability than CVE-2025-10770.
References
- https://gist.github.com/Catherines77/f15d53e9705b24cf018e5bffed3e8234 Third Party Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/66xxx/CVE-2025-66913... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2025-66913 Vendor Advisory
- https://github.com/jeecgboot/jimureport/issues/4306 Exploit Issue Tracking Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Type
CWE-94Code Injection
Timeline
Published8 Jan 2026
Updated4 Nov 2026
First seen7 Mar 2026
Track software like this
Free during beta