CVE-2026-104143 dataease CVE debrief

Who should care

Defenders responsible for data visualization and analysis tools, particularly those using DataEase, should assess exposure and apply the patch due to the high CVSS score and potential for SQL injection attacks.

Why it matters

CVE-2026-104143 is a high-severity vulnerability in DataEase that allows authenticated users to store malicious dateFormat templates, potentially leading to SQL injection attacks. Defenders should prioritize verifying exposure and applying the patch to prevent exploitation.

• Potential SQL injection attacks compromising backend database confidentiality, integrity, and availability.
• Need to verify exposure and apply the patch to prevent exploitation.
• Possible lateral movement and privilege escalation if exploited.
• Requires monitoring for suspicious SQL queries and implementing additional security measures.

Technical summary

The vulnerability exists in the dateFormat field templates of DataEase, allowing authenticated users to store crafted custom dateFormat for a dataset field. This can be used to alter generated SQL when a chart renders the field on a cross-datasource dataset, potentially compromising the confidentiality, integrity, and availability of the backend database. The issue is fixed in version 2.10.26. Defenders should prioritize verifying exposure and applying the patch due to the high CVSS score of 8.7 and the potential for SQL injection attacks. Affected product deployments should be identified, and owners assigned for follow-up.

Defensive priority

Defenders should prioritize verifying exposure and applying the patch due to the high CVSS score of 8.7 and the potential for SQL injection attacks.

Recommended defensive actions

• Verify if the current version of DataEase is prior to 2.10.26 and update to 2.10.26 or later if necessary.
• Review and restrict user permissions to prevent authenticated users from storing malicious dateFormat templates.
• Monitor for suspicious SQL queries and implement additional security measures to detect and prevent SQL injection attacks.
• Perform a thorough review of the system to identify potential entry points for SQL injection attacks.
• Implement a Web Application Firewall (WAF) to detect and prevent SQL injection attacks.
• Conduct regular security audits to identify vulnerabilities and ensure compliance with security best practices.
• Review and update incident response plans to include procedures for responding to SQL injection attacks.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and fixed version. Defenders should verify exposure by checking if the current version of DataEase is prior to 2.10.26 and review user permissions to prevent storing malicious dateFormat templates. Evidence is limited to public CVE Program and source item records. Additional verification is required to confirm affected scope and severity.

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.