CVE-2026-33083
Received Received - Intake
SQL Injection in DataEase Dataset Endpoints Enables Data Extraction

Publication date: 2026-04-16

Last updated on: 2026-04-20

Assigner: GitHub, Inc.

Description
DataEase is an open-source data visualization and analytics platform. Versions 2.10.20 and below contain a SQL injection vulnerability in the orderDirection parameter used in dataset-related endpoints including /de2api/datasetData/enumValueDs and /de2api/datasetTree/exportDataset. The Order2SQLObj class directly assigns the raw user-supplied orderDirection value into the SQL query without any validation or whitelist enforcement, and the value is rendered into the ORDER BY clause via StringTemplate before being executed against the database. An authenticated attacker can inject arbitrary SQL commands through the sorting direction field, enabling time-based blind data extraction and denial of service. This issue has been fixed in version 2.10.21.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-16
Last Modified
2026-04-20
Generated
2026-06-16
AI Q&A
2026-04-16
EPSS Evaluated
2026-06-15
NVD
CVE-2026-33083
EUVD
EUVD-2026-23282
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dataease dataease to 2.10.21 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.

Compliance Impact

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.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-33083. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart