PatchTheCVEjimureport vulnerabilities and fixes
Recent CVEs affecting jimureport, with upgrade or downgrade steps. 5 tracked.
jimureport has 5 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-01-08. Highest priority: CVE-2025-66913 (score 64/100).
- CVE-2025-8963 MEDIUM 6.3 UPGRADE A vulnerability was determined in jeecgboot JimuReport up to 2.1.1
- CVE-2025-66913 CRITICAL 9.8 UPGRADE JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC U
- CVE-2025-10771 MEDIUM 6.3 UPGRADE A vulnerability was determined in jeecgboot JimuReport up to 2.1.2
- CVE-2025-10770 MEDIUM 6.3 UPGRADE A vulnerability was found in jeecgboot JimuReport up to 2.1.2
- CVE-2024-44893 CRITICAL 9.8 DOWNGRADE An issue in the component /jeecg-boot/jmreport/dict/list of JimuReport v1.7.8 allows attacker to escalate priv
FAQ
How do I fix jimureport vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jimureport being exploited right now?
None of the tracked jimureport CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jimureport CVE should I patch first?
CVE-2025-66913 currently ranks highest (64/100): JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC U.