CVE-2025-66913: JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC URLs. The…
CVE-2025-66913 · Severity: critical · CVSS 9.8 · Published 2026-01-08
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.
No. Junglewise Threat Intelligence has no report of CVE-2025-66913 being exploited in the wild.
How severe is CVE-2025-66913?
Critical severity, with a CVSS score of 9.8, published 8 January 2026.
Which products and versions are affected?
Jeecg Jimureport. The advisory does not name versions.
Is there a fix for CVE-2025-66913?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-66913?
Check whether you run Jeecg Jimureport. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.