CVE-2025-48998: dataease · SQL Injection
Affects dataeaseSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.3 High : upgrade to 2.10.10 soon.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.10.10
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:PExploitation evidence
Disclosed: evidence found.
CVE published 3 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade dataease/dataease to 2.10.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdataease/dataeasepkg:github/dataease/dataeaseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade DataEase installations to version 2.10.10 or later to remediate this vulnerability. Since no workarounds exist, patching is the primary defense. Organizations should also audit and restrict user privileges to minimize the number of users with authenticated access capable of exploiting this vulnerability. Implement strong authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of credential compromise. Conduct thorough logging and monitoring of DataEase access and JDBC connection activities to detect any anomalous behavior indicative of exploitation attempts. Network segmentation should be employed to isolate DataEase servers from less trusted network zones, limiting exposure. Additionally, organizations should review and harden authorization controls within DataEase to ensure proper access restrictions are enforced, mitigating CWE-862 related risks. Regular security assessments and penetration testing focusing on SQL injection and deserialization vectors in DataEase deployments are recommended to identify residual risks.
Description
DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.6, a bypass of the patch for CVE-2025-27103 allows authenticated users to read and deserialize arbitrary files through the background JDBC connection. The vulnerability has been fixed in v2.10.10. No known workarounds are available.