Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege DataEase account
-
DeliveryPOST crafted PreviewSqlDTO to /de2api/datasetData/previewSql
-
ExploitInjected SQL stored in datasourceRequest.query
-
ExecutionCalciteProvider executes via prepareStatement().executeQuery()
-
ImpactRead arbitrary datasource tables from preview response
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated DataEase account (CVSS PR:L) with the ability to reach the SQL preview feature at /de2api/datasetData/previewSql and at least one configured datasource whose datasourceId the attacker can supply in PreviewSqlDTO. The attacker controls PreviewSqlDTO.sql (the injected/arbitrary SQL), datasourceId (which datasource to target), and isCross. Limiting factors: exploitation is not fully unauthenticated (low-privilege credentials are needed), impact is confined to data the configured datasource account can read (VI:N/VA:N - no write or destructive capability), and only versions prior to 2.10.23 are affected. Applies to default configurations of DataEase where the preview endpoint and datasources are available to logged-in users. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N, base 7.1) describes a network-reachable, low-complexity attack that requires low-level privileges (PR:L) and yields high confidentiality impact but no integrity or availability impact - consistent with a read-only data exfiltration flaw rather than full RCE or data tampering. No EPSS score, KEV listing, or SSVC decision was provided, so exploitation probability and automatability cannot be quantified from the input; the flaw is not confirmed to be actively exploited. The realistic priority is moderate-to-high for internet-exposed or multi-tenant DataEase deployments because any authenticated (even low-privilege) user can pivot to reading arbitrary datasource tables, but the PR:L requirement and read-only scope keep it below a critical unauthenticated-RCE tier. Note the vendor description of 'arbitrary readable datasource tables' aligns with VI:N/VA:N - this is data disclosure, not modification, so treat it as an information-exposure priority. |
| Exploit ScenarioDerived | A low-privilege authenticated DataEase user (or an attacker who has obtained any valid account) sends a crafted POST to /de2api/datasetData/previewSql with a PreviewSqlDTO whose sql field selects from a sensitive table and a valid datasourceId. DataEase decodes and executes the query via prepareStatement().executeQuery() and returns the rows in the preview response, exfiltrating data outside the user's authorized datasets. The network attack vector and low complexity make this trivial to script once credentials are held; no public POC was provided but the fix commit is public. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 15, 2026
Arbitrary SQL read access in DataEase before 2.10.23 lets authenticated users abuse the SQL preview feature (/de2api/datasetData/previewSql) to run attacker-supplied queries against any configured datasource. Because DatasetDataManage.previewSql passes the decoded PreviewSqlDTO.sql straight into datasourceRequest.query and CalciteProvider.fetchResultField executes it via prepareStatement().executeQuery(), an attacker can read any table the datasource account can access and receive the rows in the preview response. No public exploit identified at time of analysis, but the fix commit and advisory are public, making the flaw easy to reverse-engineer.
RemediationAI
Vendor-released patch: upgrade to DataEase 2.10.23, which is the fixed release (https://github.com/dataease/dataease/releases/tag/v2.10.23); the corrective change is in commit 22930a493d900fe3d8084b3dd4c0125abdb2a847, which parameterizes SQL-variable default values via prepared statements in DeSqlparserUtils and SqlparserUtils. Review the advisory GHSA-j4v5-5gcx-cvfc for details. If immediate upgrade is not possible, restrict network access to the /de2api/datasetData/previewSql endpoint (for example via a reverse-proxy/WAF rule or network ACL) so only trusted administrators can reach the SQL preview feature - trade-off: this disables SQL-based dataset preview for legitimate low-privilege analysts. Additionally, tighten the database accounts configured as DataEase datasources to least-privilege, read-scoped accounts limited to only the tables needed, which caps the blast radius of any query that does reach the JDBC layer, at the cost of some dataset flexibility.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
DataEase is an open-source data visualization and business intelligence platform (io.dataease) that connects to external SQL datasources and lets users build datasets. The vulnerable path is the SQL preview capability: the DatasetDataApi.previewSql / previewSqlCheck controller accepts a PreviewSqlDTO containing raw sql, a datasourceId, and an isCross flag, and DatasetDataManage.previewSql stores the decoded SQL in datasourceRequest.query, which CalciteProvider.fetchResultField then runs through JDBC prepareStatement(...).executeQuery(). This is a classic CWE-89 (SQL Injection / improper neutralization of SQL) issue rooted in trusting client-supplied SQL and variable default values rather than parameterizing them - the fix in DeSqlparserUtils/SqlparserUtils replaces raw default-value string concatenation with a buildPreparedSqlFragmentForDefaultValue path that binds values as prepared-statement parameters. The single CPE cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* covers all versions prior to 2.10.23.
Know when Dataease gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable preview endpoint with low complexity but requires a low-privilege authenticated account (PR:L); read-only data disclosure gives C:H with I:N and A:N.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase SQL preview exposes DatasetDataApi.previewSql/previewSqlCheck through /de2api/datasetData/previewSql, accepts PreviewSqlDTO.sql, PreviewSqlDTO.datasourceId, and PreviewSqlDTO.isCross, then DatasetDataManage.previewSql stores decoded SQL in datasourceRequest.query and CalciteProvider.fetchResultField executes it with prepareStatement(...).executeQuery(), allowing arbitrary readable datasource tables to be queried and returned in preview responses. This issue is fixed in version 2.10.23.
Executive ViewAI
DataEase versions prior to 2.10.23 allow authenticated users to bypass access controls and read arbitrary data from connected databases. This directly exposes sensitive customer data, financial records, and operational information accessed through the analytics platform. Organizations must urgently identify and patch vulnerable DataEase deployments to prevent insider data theft.
Vendor-released patch: DataEase 2.10.23. Interim: Implement network-level access restrictions between DataEase and production databases, disable or restrict the SQL preview feature at the application level, and enable detailed audit logging on all datasource queries to detect anomalous access patterns.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
DataEase is an open source business intelligence and data visualization tool. Prior to version 2.10.11, a threat actor m
Auth bypass in DataEase via CVE-2025-49001 patch evasion. PoC available.
Auth bypass in DataEase BI tool before 2.10.10.
A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.
A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.
A remote code execution vulnerability in DataEase (CVSS 9.8). Risk factors: public PoC available.
DataEase data visualization tool prior to 2.10.19 uses MD5-hashed passwords without salting, allowing attackers to crack
DataEase is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r
DataEase is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r
DataEase is an open source data visualization and analysis tool. Rated critical severity (CVSS 9.8), this vulnerability
Dataease is an open source data visualization and analysis tool. Rated critical severity (CVSS 9.8), this vulnerability
Dataease is an open source data visualization analysis tool. Rated critical severity (CVSS 9.8), this vulnerability is r
EUVD-2026-44778
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB