# CVE-2025-48999: Dataease Redshift Data Source JDBC Connection Parameters Not Verified Leads to RCE Vulnerability

> Attackers can achieve remote code execution in DataEase by injecting malicious JDBC parameters into Redshift data source configurations.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-6pq2-6q8x-mp2r

## What is CVE-2025-48999?

CVE-2025-48999 is a medium-severity code injection vulnerability in Dataease Dataease, published on 3 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DataEase is an open source business intelligence and data visualization tool. A bypass of CVE-2025-46566's patch exists in versions prior to 2.10.10. In a malicious payload, `getUrlType()` retrieves `hostName`. Since the judgment statement returns false, it will not enter the if statement and will not be filtered. The payload can be directly concatenated at the replace location to construct a malicious JDBC statement. Version 2.10.10 contains a patch for the issue.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Dataease Dataease.

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

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

## Is CVE-2025-48999 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48999 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-48999 and fix it if it is affected.

What it is: CVE-2025-48999 is a medium-severity code injection vulnerability in Dataease Dataease, published on 3 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48999 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-48999/ (Markdown: https://insights.sbomify.com/CVE-2025-48999/index.md)
```

## Sources

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

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