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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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.
Which versions are affected by CVE-2025-48999?
It affects 1 product.
Products include 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.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
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 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Sources
Also known as GHSA-6pq2-6q8x-mp2r.