CVE-2026-104142 dataease CVE debrief

Who should care

Defenders responsible for DataEase installations, particularly those using versions prior to 2.10.26, should assess exposure and prioritize patching to prevent exploitation. Defenders should also review and validate backend database configurations, monitor for suspicious activity, and review compensating controls for exposed systems while remediation is scheduled and verified. Additionally, defenders should check relevant monitoring, detection, and logs  

Why it matters

CVE-2026-104142 is a stored SQL injection vulnerability in DataEase that allows authenticated users to compromise the confidentiality, integrity, and availability of the configured backend database. Defenders should prioritize patching to version 2.10.26 or later to prevent exploitation.

• Potential unauthorized access to backend database data
• Possible data tampering or modification
• Risk of database availability issues
• Need for verification of backend database configurations

Technical summary

The vulnerability allows authenticated users to store crafted FieldGroupDTO.min, FieldGroupDTO.max, FieldGroupDTO.startTime, or FieldGroupDTO.endTime values in dataset group-field binning definitions. These values are inserted into generated CASE expressions without validation, leading to unparameterized backend query execution when a chart uses the field. This can lead to unparameterized backend query execution when a chart uses the field, compromising the confidentiality, integrity, and availability of the configured backend database. The issue is fixed in version 2.10.26. Authenticated users can store malicious values in dataset group-field binning definitions, which are then inserted into generated CASE  

Defensive priority

Defenders should prioritize patching to version 2.10.26 or later to prevent exploitation.

Recommended defensive actions

• Patch DataEase to version 2.10.26 or later
• Review and validate backend database configurations
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and fixed version. The vulnerability allows authenticated users to store crafted FieldGroupDTO.min, FieldGroupDTO.max, FieldGroupDTO.startTime, or FieldGroupDTO.endTime values in dataset group-field binning definitions. These values are inserted into generated CASE expressions without validation, leading to unparameterized backend query execution when a chart uses the field. Defenders should verify backend database  

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.