# CVE-2025-27103: Dataease Mysql JDBC Connection Parameters Not Being Verified Leads to Arbitrary File Read Vulnerability​


- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Mar 2025
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-v4gg-8rp3-ccjx

## What is CVE-2025-27103?

CVE-2025-27103 is a high-severity vulnerability in Dataease Dataease, published on 13 Mar 2025. 

### Official description

DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.6, a bypass for the patch for CVE-2024-55953 allows authenticated users to read and deserialize arbitrary files through the background JDBC connection. The vulnerability has been fixed in v2.10.6. No known workarounds are available.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Dataease Dataease.

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

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

## Is CVE-2025-27103 being exploited?

There is no known exploitation of CVE-2025-27103 in the wild and no public exploit code.

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

What it is: CVE-2025-27103 is a high-severity vulnerability in Dataease Dataease, published on 13 Mar 2025. 
Exploitation: There is no known exploitation of CVE-2025-27103 in the wild and no public exploit code.

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-27103/ (Markdown: https://insights.sbomify.com/CVE-2025-27103/index.md)
```

## Sources

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

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