CVE-2026-45535 dataease CVE debrief

Who should care

Users of DataEase versions prior to 2.10.23 should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to version 2.10.23 or later, and restricting access to sensitive datasets. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability and take necessary actions to protect their systems.

Technical summary

The vulnerability exists in DataEase SQL-type datasets, where attacker-controlled SQL variable defaultValue entries, such as ${var}, are stored. When a user with dataset read permission accesses the dataset, the SqlparserUtils.handleVariableDefaultValue() function inserts these entries using String.replace() without escaping or parameterization, leading to stored SQL injection. This issue is fixed in version 2.10.23. The vulnerability has a high CVSS score of 8.7 and is considered a high-severity issue.

Defensive priority

High

Recommended defensive actions

• Upgrade to DataEase version 2.10.23 or later
• Restrict access to sensitive datasets
• Monitor for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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

Evidence notes

The CVE record was published on 2026-07-15T20:17:04.723Z and has not been modified since then. The NVD entry is currently Deferred. There is limited evidence available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability exists in DataEase SQL-type datasets, where attacker-controlled SQL variable defaultValue entries, such as ${var}, are stored. When a user with dataset read permission accesses the dataset, the SqlparserUtils.handleVariableDefaultValue() function inserts these entries using String.replace() without escaping or parameterization, leading to stored SQL injection. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

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.