dbcve.org
DataeaseApplication

CVE-2025-57772

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-25
Fix available
A fix is available. Upgrade to 2.10.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.12, there is a H2 JDBC RCE bypass in DataEase. If the JDBC URL meets criteria, the getJdbcUrl method is returned, which acts as the getter for the JdbcUrl parameter provided. This bypasses H2's filtering logic and returns the H2 JDBC URL, allowing the "driver":"org.h2.Driver" to specify the H2 driver for the JDBC connection. The vulnerability has been fixed in version 2.10.12.

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 confidence

DataEase prior to version 2.10.12 contains an H2 JDBC RCE bypass. The getJdbcUrl method acts as a getter for the JdbcUrl parameter and returns the JDBC URL in a way that bypasses H2's filtering logic. This allows attackers to specify 'driver':'org.h2.Driver' in the JDBC connection, enabling remote code execution.

MitigationUpgrade DataEase to version 2.10.12 or later to patch the H2 JDBC RCE bypass. If immediate upgrade is not possible, restrict network access to DataEase interfaces and audit JDBC connection configurations.

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
DataeaseApplication
Affected:< 2.10.12

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataEase version
    Log into the DataEase web interface and navigate to 'About' or 'System Settings' to view the installed version. If deployed via Docker, run 'docker ps' to find the container, then 'docker inspect <container>' or check the image tag for the version.
    Affected if The displayed version is below 2.10.12 (e.g., 2.10.11, 2.10.10, etc.)
  2. Confirm JDBC connection feature is accessible
    In the DataEase web interface, navigate to the data source or connection configuration section where users can add or edit JDBC database connections.
    Affected if Users with appropriate permissions can create or modify JDBC connection configurations through the web interface
  3. Check for H2 database connections
    Review existing data source configurations in DataEase for any connections using the H2 database driver (org.h2.Driver) or H2 JDBC URLs (typically starting with 'jdbc:h2:').
    Affected if Any JDBC data source is configured with H2 driver or H2 JDBC URL string
  4. Verify network exposure of DataEase
    Check if the DataEase web interface is accessible from untrusted networks by reviewing firewall rules, reverse proxy configurations, or cloud security group settings.
    Affected if DataEase HTTP/HTTPS ports (default 8080, 443, or custom) are exposed to the public internet or untrusted internal networks

A user is affected if their DataEase version is below 2.10.12 AND the web interface with JDBC connection configuration is accessible (especially over network), allowing potential attackers to inject a malicious JDBC connection with the H2 driver to achieve RCE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.10.12 or later
Fixed in 2.10.12
Vendor patch github.com →
Interim mitigation

Upgrade DataEase to version 2.10.12 or later to patch the H2 JDBC RCE bypass. If immediate upgrade is not possible, restrict network access to DataEase interfaces and audit JDBC connection configurations.

Recommended fix High confidence

2.10.12

  1. Upgrade DataEase to version 2.10.12 or later to address the H2 JDBC RCE bypass vulnerability
  2. After upgrade, verify that the JDBC URL filtering is working correctly and the getJdbcUrl method bypass is no longer present
  3. Review DataEase release notes for version 2.10.12 to confirm all security patches are included

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dataease Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57772 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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