CVE-2025-66913
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJimuReport 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJimuReport through v2.1.3 is vulnerable to remote code execution via user-controlled H2 JDBC URLs. The application directly passes attacker-supplied JDBC connection strings to the H2 database driver without sanitization, enabling attackers to leverage H2 directives (such as RUNSCRIPT or CREATE ALIAS) to execute arbitrary Java code on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify JimuReport installationLocate the JimuReport application deployment in your environment - check application directories, WAR files, or container images where the Java application is deployed. Look for jimureport or jeecg-related artifacts.Affected if JimuReport is present in your environment
-
Determine installed versionCheck the application's version file, build descriptor (pom.xml, build.gradle), or the version displayed in the web interface. Compare your version number to the affected range: versions 2.1.3 and below are vulnerable.Affected if Installed version is 2.1.3 or lower
-
Verify H2 database is in useInspect the application configuration files (application.properties, application.yml) for H2 database connections. Look for 'jdbc:h2:' connection strings in your datasource configuration.Affected if H2 database is configured as the application's datasource
-
Check for user-exposed JDBC URL inputReview the application's web interfaces, APIs, and configuration screens for features that allow users to specify custom JDBC connection URLs, particularly in database connection testing or reporting data source configuration areas.Affected if User-controllable JDBC URL parameters are accessible without strict validation
-
Inspect H2 security settingsExamine the H2 database connection string for security-related parameters such as ALLOW_LITERALS, NON_AUTHENTICATED, or whether dangerous H2 functions (RUNSCRIPT, CREATE ALIAS, SHUTDOWN) are explicitly disabled in the connection configuration.Affected if H2 connection allows RUNSCRIPT, CREATE ALIAS, or similar dangerous directives without restriction
Your environment is affected if JimuReport version 2.1.3 or lower is running with H2 database and user-controlled JDBC URLs can be submitted to the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict or eliminate user-controlled JDBC URL input; if required, implement strict allowlist validation of JDBC URL parameters. Until a patched version is available, network-segment the application and disable H2's dangerous functions.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data