# CVE-2025-62420: DataEase vulnerable to remote code execution via H2 JDBC driver bypass

> An authenticated attacker can bypass JDBC driver checks to execute arbitrary code via malicious JDBC connections in DataEase.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-7wcv-j6gc-qc7q

## What is CVE-2025-62420?

CVE-2025-62420 is a high-severity unsafe deserialization vulnerability in Dataease Dataease, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DataEase is a data visualization and analytics platform. In DataEase versions through 2.10.13, a JDBC driver bypass vulnerability exists in the H2 database connection handler. The getJdbc function in H2.java checks if the jdbcUrl starts with jdbc:h2 but returns a separate jdbc field as the actual connection URL. An attacker can provide a jdbcUrl that starts with jdbc:h2 while supplying a different jdbc field with an arbitrary JDBC driver and connection string. This allows an authenticated attacker to trigger arbitrary JDBC connections with malicious drivers, potentially leading to remote code execution. The vulnerability is fixed in version 2.10.14. No known workarounds exist.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-62420?

It affects 1 product.


Products: Dataease Dataease.

## How do I fix CVE-2025-62420?

No fix has been published for CVE-2025-62420 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62420 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62420 exists.

## Other vulnerabilities in Dataease Dataease

- [CVE-2024-57707](https://insights.sbomify.com/CVE-2024-57707/): Code injection in n/a (critical 9.8)
- [CVE-2024-46997](https://insights.sbomify.com/CVE-2024-46997/): DataEase's H2 datasource has a remote command execution risk (critical 9.8)
- [CVE-2023-33963](https://insights.sbomify.com/CVE-2023-33963/): DataEase data source has deserialization vulnerability (critical 9.8)
- [CVE-2023-28437](https://insights.sbomify.com/CVE-2023-28437/): SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed (critical 9.8)
- [CVE-2022-39312](https://insights.sbomify.com/CVE-2022-39312/): Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62420 and fix it if it is affected.

What it is: CVE-2025-62420 is a high-severity unsafe deserialization vulnerability in Dataease Dataease, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62420 exists.

Affected product: Dataease Dataease. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62420/ (Markdown: https://insights.sbomify.com/CVE-2025-62420/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62420
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62420
- OSV: https://osv.dev/vulnerability/CVE-2025-62420

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62420/
Summaries are generated and may contain mistakes; the official description above is the record.