Read the docs
TI-2026-74414 Aliases CVE-2026-104143

Stored SQL injection in DataEase via dateFormat field templates

Priority LOW 39CWE-289Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

DataEase before 2.10.26 is affected. An authenticated user with low privileges can store a crafted dateFormat for a dataset field, which is inserted without validation into SQL date conversion templates, causing stored SQL injection. When a chart renders that field on a cross-datasource dataset, the crafted format alters the generated SQL, which can compromise the confidentiality, integrity and availability of the backend database.

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 a crafted custom dateFormat for a dataset field. DatasetTableFieldDTO.dateFormat is inserted without validation into date conversion templates used by Dimension2SQLObj, CustomWhere2Str, Field2SQLObj, WhereTree2Str, and ExtWhere2Str. When a chart renders the field on a cross-datasource dataset, Calcite parsing is bypassed and the crafted format can directly alter the generated SQL. On a single-datasource dataset, exploitation additionally requires the payload to survive Calcite reserialization as a valid string literal. Successful exploitation can compromise the confidentiality, integrity, and availability of the backend database. This issue is fixed in version 2.10.26.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00264 18th percentileScored 2026-11-07
Fix Fixed dataease (dataease): 2.10.26

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
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.

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-104143
  2. 2026-10-15 CISA SSVC decision points changed
  3. 2026-10-15 Priority changed: MEDIUM → LOW

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