CVE-2026-50030: DataEase: Arbitrary SQL execution in preview path (direct data disclosure)
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.
Security readout for executives and security teams
Plain-English summary
DataEase versions before 2.10.23 can let a logged-in user run arbitrary SQL through a dataset preview feature. The main risk is data exposure: readable tables in connected datasources may be queried and returned by the application. The source bundle identifies a fixed version but does not state active exploitation.
Executive priority
Prioritize patching if DataEase connects to production, customer, financial, security, or regulated datasets. This is a high confidentiality risk with low privilege requirements, but current provided evidence does not show known active exploitation.
Technical view
The preview path /de2api/datasetData/previewSql accepts PreviewSqlDTO.sql, datasourceId, and isCross. Prior to 2.10.23, decoded SQL was stored in datasourceRequest.query and executed through CalciteProvider.fetchResultField using prepareStatement(...).executeQuery(). CVSS 4.0 is 7.1 with network access, low privileges, no user interaction, and high confidentiality impact.
Likely exposure
DataEase deployments below 2.10.23 are exposed where authenticated low-privilege users can reach the dataset SQL preview API and connected datasources contain readable sensitive data. The bundle does not specify exact role requirements, default exposure, or datasource-specific limits.
Exploitation context
The sources do not state active exploitation, and the bundle marks KEV as false. Exploitation would require network reachability and low privileges. The described impact is direct disclosure of data accessible through configured datasources, not system takeover.
Researcher notes
Evidence is specific to DataEase before 2.10.23 and the SQL preview flow. Treat role boundaries and datasource scoping as validation questions because the bundle does not define authorization details beyond PR:L. Avoid assuming broader write, integrity, or availability impact.
Mitigation direction
Upgrade DataEase to version 2.10.23 or later.
Review the GitHub advisory, fixing commit, and release notes.
Restrict DataEase access to trusted authenticated users until patched.
Limit datasource accounts to least-privilege read access.
Review preview SQL activity for unusual queries or data access.
Validation and detection
Inventory DataEase instances and confirm their running versions.
Check whether /de2api/datasetData/previewSql is reachable by low-privilege users.
Review configured datasources for sensitive readable tables.
Confirm upgrade to 2.10.23 in deployment records.
Review application logs for suspicious preview SQL requests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.