DataEase: Stored SQL Injection via dateFormat field templates
dataease
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| dataease dataease |
| No fix yet |
Original description
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.
From the CVE record · GitHub_M
References
- github.com/dataease/dataease/security/advisories/GHSA-h32f-m89w-g35f
- github.com/dataease/dataease/commit/c8cde16056a9e46aa4866ded94db2b250758b337
- github.com/dataease/dataease/releases/tag/v2.10.26
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104143.json
- nvd.nist.gov/vuln/detail/CVE-2026-104143