CVE-2026-33122
Received Received - Intake

SQL Injection in DataEase API Allows Database Information Disclosure

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 API datasource update process. When a new table definition is added during a datasource update via /de2api/datasource/update, the deTableName field from the user-submitted configuration is passed to DatasourceSyncManage.createEngineTable, where it is substituted into a CREATE TABLE statement template without any sanitization or identifier escaping. An authenticated attacker can inject arbitrary SQL commands by crafting a deTableName that breaks out of identifier quoting, enabling error-based SQL injection that can extract database information. 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-07-06
AI Q&A
2026-04-16
EPSS Evaluated
2026-07-05
NVD
CVE-2026-33122
EUVD
EUVD-2026-23290

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 the API datasource update process improperly handles the deTableName field. Specifically, when a new table definition is added via the /de2api/datasource/update endpoint, the deTableName value is directly inserted into a CREATE TABLE SQL statement without sanitization or escaping. This allows an authenticated attacker to craft a deTableName that breaks out of the intended SQL identifier quoting, enabling error-based SQL injection to extract database information.

The issue has been fixed in version 2.10.21.

Impact Analysis

An attacker who is authenticated can exploit this vulnerability to perform SQL injection attacks, which may allow them to extract sensitive database information. This can lead to unauthorized data disclosure, potentially compromising the confidentiality and integrity of the data managed by the DataEase platform.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade DataEase to version 2.10.21 or later, where the SQL injection issue has been fixed.

Ensure that only authenticated users with appropriate privileges can access the /de2api/datasource/update API endpoint to reduce risk.

Compliance Impact

The vulnerability allows an authenticated attacker to perform error-based SQL injection, potentially extracting sensitive database information. This exposure of sensitive data could lead to non-compliance with data protection standards and regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access.

Since the vulnerability enables unauthorized data extraction through SQL injection, it increases the risk of data breaches, which are subject to regulatory reporting and penalties under these standards.

Chat Assistant

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

EPSS Chart