CVE-2026-33121
SQL Injection in DataEase API Allows Database Information Disclosure
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, an open-source data visualization and analytics platform, in versions 2.10.20 and below. It is a SQL injection vulnerability found in the API datasource saving process. Specifically, the deTableName field from the Base64-encoded datasource configuration is used to build a DDL SQL statement through simple string replacement without sanitizing or escaping the table name. An authenticated attacker can exploit this by crafting a deTableName value that breaks out of the identifier quoting, allowing them to inject arbitrary SQL commands.
This injection is error-based, meaning the attacker can extract information from the database, such as the MySQL version, by triggering SQL errors. The issue was fixed in version 2.10.21.
How can this vulnerability impact me? :
This vulnerability can have serious impacts because it allows an authenticated attacker to execute arbitrary SQL commands on the database. This can lead to unauthorized access to sensitive data, data leakage, or manipulation of the database.
Since the attacker can extract database information such as the MySQL version, it may also facilitate further attacks or exploitation of other vulnerabilities.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in DataEase version 2.10.21. The immediate step to mitigate this vulnerability is to upgrade your DataEase installation to version 2.10.21 or later.
Since the vulnerability involves SQL injection via the deTableName field in the API datasource saving process, avoid using or accepting untrusted input in this field until the upgrade is applied.
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 extracting sensitive database information. Such unauthorized data access can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access or disclosure.
Therefore, if exploited, this vulnerability could compromise compliance with standards that mandate strict data security controls, as it undermines the confidentiality and integrity of stored data.