CVE-2026-33083
SQL Injection in DataEase Dataset Endpoints 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
Can you explain this vulnerability to me?
This vulnerability exists in DataEase versions 2.10.20 and below, where a SQL injection flaw is present in the orderDirection parameter used in certain dataset-related API endpoints.
The Order2SQLObj class directly uses the raw user input from the orderDirection parameter in the SQL query without validating or restricting it, allowing an attacker to inject arbitrary SQL commands.
This injection occurs in the ORDER BY clause of the SQL query, which is constructed using StringTemplate, and can be exploited by an authenticated attacker.
The impact includes the ability to perform time-based blind data extraction and cause denial of service.
The issue was fixed in version 2.10.21.
How can this vulnerability impact me? :
An attacker who is authenticated can exploit this vulnerability to inject arbitrary SQL commands through the orderDirection parameter.
This can lead to unauthorized extraction of data using time-based blind SQL injection techniques.
Additionally, the attacker can cause denial of service, potentially disrupting the availability of the DataEase platform.
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.
An immediate step to mitigate this vulnerability is to upgrade DataEase to version 2.10.21 or later.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an authenticated attacker to perform SQL injection, potentially leading to unauthorized data extraction and denial of service. Such unauthorized access and data exposure could impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access.
However, the provided information does not explicitly detail the compliance implications or specific regulatory impacts of this vulnerability.