Read the docs
TI-2026-74413 Aliases CVE-2026-104142

Stored SQL injection in DataEase group-field binning bounds

Priority HIGH 73CWE-89Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
SQL injection
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-89.

Summary

DataEase versions before 2.10.26 are affected. Authenticated users can store crafted binning bounds and time values in dataset group-field definitions, and these values are inserted without validation into generated SQL expressions (CWE-89). An authenticated user with low privileges can run SQL against the configured backend database when a chart uses the field, which can affect its confidentiality, integrity and availability.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00351 28th percentileScored 2026-11-07
Fix Fixed dataease (dataease): 2.10.26

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
dataeasedataeasebefore 2.10.262.10.26Patch availableCNA
  • dataease Vendordataease Affected before 2.10.26 Fixed in 2.10.26 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*——dataease
  • cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:* Versions — — ·dataease

Remediation

Upgrade DataEase to version 2.10.26, which fixes this issue. Versions before 2.10.26 are affected.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA dataease (dataease) Fixed in 2.10.26

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-104142
  2. 2026-10-15 CISA SSVC decision points changed
  3. 2026-10-15 Priority changed: MEDIUM → HIGH

References

Other 3

  • TI-2024-38037 An issue in DataEase v1 allows an attacker to execute arbitrary code via the user account and password components. CVSS 3.1CRITICAL 9.8
  • TI-2023-12981 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed CVSS 3.1CRITICAL 9.8
  • TI-2022-18688 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2026-24677 Dataease: Redshift JDBC RCE Bypass CVSS 4.0CRITICAL 9.3
  • TI-2026-24674 DataEase SQL Injection Vulnerability CVSS 4.0CRITICAL 9.3
  • TI-2024-37398 DataEase has an unauthorized vulnerability CVSS 4.0CRITICAL 9.3
See all 116 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences