CVE-2025-66913: jimureport · Code Injection
Affects jimureportSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.jeecg/jimureportpkg:maven/org.jeecg/jimureportOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Immediate mitigation steps include restricting access to JimuReport interfaces that process JDBC URLs, ideally limiting them to trusted internal networks. Implement strict input validation and sanitization on all user-supplied JDBC URL parameters to prevent malicious directives from being processed. Monitor logs for suspicious JDBC URL patterns or unusual database driver activity. If possible, disable or sandbox the H2 database driver features that allow execution of arbitrary code via JDBC URLs. Organizations should engage with JimuReport vendors or maintainers to obtain patches or updates addressing this vulnerability. Until patches are available, consider deploying web application firewalls (WAFs) with custom rules to detect and block malicious JDBC URL payloads. Conduct thorough security assessments and penetration testing focused on this attack vector. Educate developers and administrators about the risks of passing user-controlled inputs directly to database drivers. Finally, maintain robust incident response plans to quickly contain and remediate any exploitation attempts.
Description
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.