# CVE-2025-49002: Dataease H2 Database Remote Code Execution (RCE) Bypass Vulnerability

> Attackers can bypass security patches to execute arbitrary code in DataEase by exploiting case-insensitive command filtering flaws.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 4 Jun 2025

## What is CVE-2025-49002?

CVE-2025-49002 is a high-severity code injection vulnerability in Dataease Dataease, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DataEase is an open source business intelligence and data visualization tool. Versions prior to version 2.10.10 have a flaw in the patch for CVE-2025-32966 that allow the patch to be bypassed through case insensitivity because INIT and RUNSCRIPT are prohibited. The vulnerability has been fixed in v2.10.10. No known workarounds are available.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Dataease Dataease.

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

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

## Is CVE-2025-49002 being exploited?

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

Public exploit code:

- 飞致云 DataEase Postgresql JDBC Bypass 远程代码执行漏洞 CVE-2025-49002 漏洞类型 RCE (github_poc): https://github.com/Feng-Huang-0520/DataEase_Postgresql_JDBC_Bypass-CVE-2025-49002
- https://github.com/jiuzui129-arch/CVE-2025-49002 (github_poc): https://github.com/jiuzui129-arch/CVE-2025-49002
- DataEase - Remote Code Execution (nuclei): http/cves/2025/CVE-2025-49002.yaml

## 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-49002 and fix it if it is affected.

What it is: CVE-2025-49002 is a high-severity code injection vulnerability in Dataease Dataease, published on 3 Jun 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-49002 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-49002/ (Markdown: https://insights.sbomify.com/CVE-2025-49002/index.md)
```

## Sources

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

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