CVE-2026-104142
Deferred Deferred - Pending Action

Stored SQL Injection in DataEase Prior to 2.10.26

Publication date: 2026-10-14

Last updated on: 2026-10-15

Assigner: GitHub, Inc.

Description
DataEase is an open source data visualization and analysis tool. Prior to 2.10.26, authenticated users can store crafted FieldGroupDTO.min, FieldGroupDTO.max, FieldGroupDTO.startTime, or FieldGroupDTO.endTime values in dataset group-field binning definitions. Utils.transGroupFieldToSql inserts these free-form values into generated CASE expressions without validation, and the resulting SQL can reach unparameterized backend query execution when a chart uses the field. This stored SQL injection can compromise the confidentiality, integrity, and availability of the configured backend database. This issue is fixed in version 2.10.26.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-14
Last Modified
2026-10-15
Generated
2026-10-19
AI Q&A
2026-10-15
EPSS Evaluated
2026-10-18
NVD
CVE-2026-104142
EUVD
EUVD-2026-101555

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dataease dataease < 2.10.26

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 is a stored SQL injection vulnerability in DataEase, an open-source data visualization tool. Authenticated users can inject malicious SQL payloads into specific fields (min, max, startTime, endTime) of dataset group-field binning definitions. These values are later used to construct SQL queries without proper validation or escaping, allowing the payload to execute directly on the backend database when a chart is rendered.

Detection Guidance

Check DataEase versions prior to 2.10.26 for signs of suspicious field group definitions. Inspect logs for POST requests to /datasetField/save with unusual min, max, startTime, or endTime values. Monitor backend database queries for unparameterized CASE expressions.

Impact Analysis

An attacker could exploit this to read, modify, or delete sensitive data in the backend database, execute administrative operations, or cause denial-of-service conditions. Since the payload is stored and triggered when a chart is viewed, the impact depends on the database permissions and data stored in the system.

Compliance Impact

This vulnerability could lead to unauthorized access or exposure of personal or sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Organizations using affected versions may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Upgrade DataEase to version 2.10.26 or later immediately. Review and remove any untrusted field group definitions. Implement input validation for all user-supplied data in dataset configurations.

Chat Assistant

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

EPSS Chart