CVE-2026-33082
SQL Injection in DataEase Dataset Export Enables Data Extraction
Publication date: 2026-04-16
Last updated on: 2026-04-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dataease | dataease | to 2.10.21 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is a SQL injection in DataEase versions 2.10.20 and below, which allows attackers to execute arbitrary SQL commands. This can lead to unauthorized access to sensitive data stored in the database.
Such unauthorized data access can result in violations of data protection regulations and standards like GDPR and HIPAA, which require strict controls to protect personal and sensitive information from unauthorized disclosure or manipulation.
Therefore, if exploited, this vulnerability could compromise compliance with these regulations by exposing or altering protected data.
Can you explain this vulnerability to me?
This vulnerability exists in DataEase versions 2.10.20 and below, specifically in the dataset export functionality. It is a SQL injection vulnerability caused by the expressionTree parameter in the POST /de2api/datasetTree/exportDataset endpoint. The parameter is deserialized into a filtering object and passed to a function that translates filters into SQL queries. User-controlled values in "like" filter terms are directly concatenated into SQL fragments without proper sanitization, allowing an attacker to inject arbitrary SQL commands.
This enables blind SQL injection attacks, such as time-based extraction of database information, where an attacker can infer data by observing response times. The issue has been fixed in version 2.10.21.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database used by DataEase. This can lead to unauthorized access to sensitive data, data leakage, data modification, or even deletion.
Because it is a blind SQL injection, attackers can extract information from the database without direct visibility, potentially compromising the confidentiality and integrity of the data.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability exists in DataEase versions 2.10.20 and below and has been fixed in version 2.10.21.
The immediate step to mitigate this vulnerability is to upgrade DataEase to version 2.10.21 or later.