CVE-2026-45320
Deferred Deferred - Pending Action

SQL Injection in DataEase Dashboard

Publication date: 2026-07-15

Last updated on: 2026-07-17

Assigner: GitHub, Inc.

Description
DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase dashboard SQL variables such as ${deptId} are processed by SqlparserUtils.transFilter(), whose final branch returns raw user input for non-in and non-between operators before SubstitutedSql.replace("${var}", value) splices it into dashboard SQL, allowing authenticated users who can view a dashboard to inject SQL against integrated datasources. This issue is fixed in version 2.10.23

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-15
Last Modified
2026-07-17
Generated
2026-08-06
AI Q&A
2026-07-16
EPSS Evaluated
2026-08-04
NVD
CVE-2026-45320
EUVD
EUVD-2026-44783

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dataease dataease to 2.10.23 (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

CVE-2026-45320 is a high-severity SQL injection vulnerability in DataEase, an open-source data visualization tool. The flaw exists in the transFilter() function in SqlparserUtils.java, which fails to properly sanitize user input for SQL variable placeholders like ${deptId} in dashboard queries. When non-in or non-between operators are used, the function returns raw user input without escaping, allowing attackers to inject malicious SQL payloads.

Detection Guidance

To detect this vulnerability, check if your DataEase instance is running a version prior to 2.10.23. Use commands like 'curl -s http://<target>/api/version' or inspect the application's version in the admin panel. Look for SQL injection attempts in logs by searching for patterns like '${deptId}' or malicious SQL payloads in dashboard queries.

Impact Analysis

Authenticated users with dashboard access can exploit this vulnerability to inject SQL queries, potentially accessing or modifying database contents via UNION-based or time-based blind injection. This could lead to unauthorized data exposure, manipulation, or deletion. Additionally, administrators could achieve remote code execution by uploading a malicious JDBC driver JAR file.

Compliance Impact

This vulnerability could lead to unauthorized access or modification of sensitive data, violating GDPR and HIPAA requirements for data protection and integrity. Organizations using affected DataEase versions may face compliance breaches, legal penalties, and reputational damage due to potential data breaches or loss of data confidentiality.

Mitigation Strategies

Immediately upgrade DataEase to version 2.10.23 or later. If upgrading is not possible, restrict dashboard access to trusted users only and disable non-essential datasource integrations. Monitor network traffic for suspicious SQL queries or unauthorized database access attempts.

Chat Assistant

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

EPSS Chart