CVE-2026-45535
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase SQL-type datasets store attacker-controlled SQL variable defaultValue entries such as ${var} and SqlparserUtils.handleVariableDefaultValue() inserts them with String.replace() without escaping or parameterization, causing stored SQL injection whenever a user with dataset read permission accesses the dataset. This issue is fixed in version 2.10.23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDataEase versions prior to 2.10.23 contain a stored SQL injection vulnerability in SQL-type datasets. Attackers can inject malicious SQL through dataset variable defaultValue entries (such as ${var}), which SqlparserUtils.handleVariableDefaultValue() inserts directly using String.replace() without escaping or parameterization. When any user with dataset read permission accesses the affected dataset, the stored malicious SQL executes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed DataEase versionAccess the DataEase admin interface or check the application startup logs to identify the running version number. Compare this to 2.10.23.Affected if The installed version is earlier than 2.10.23
-
Identify SQL-type datasetsNavigate to the dataset management section in the DataEase UI or query the backend database for datasets where the type field indicates SQL-based datasets.Affected if SQL-type datasets exist in the environment
-
Inspect dataset variable defaultValue entriesExamine each SQL-type dataset configuration for variable definitions. Look for entries in the defaultValue field that contain ${var} syntax or similar variable placeholders.Affected if Any dataset contains variable defaultValue entries using ${variable} syntax
-
Verify potential injection patterns in defaultValueReview the defaultValue content for unescaped SQL fragments, quotes, semicolons, or OR/UNION keywords that could indicate injection attempts.Affected if The defaultValue fields contain raw SQL syntax without proper escaping or parameterization
-
Check dataset read permissionsReview the permission configuration for each affected dataset to determine which users or roles have read access to the datasets with variable defaultValue entries.Affected if Users with dataset read permissions exist and affected datasets contain variable defaultValue entries
The environment is affected if DataEase version is prior to 2.10.23 AND SQL-type datasets exist with variable defaultValue entries that could be exploited through the unsanitized String.replace() behavior.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade DataEase to version 2.10.23 or later, which contains the fix for proper SQL variable handling.
2.10.23
- Check current DataEase version to confirm vulnerability (versions prior to 2.10.23 are affected)
- Back up all existing DataEase data, configurations, and database
- Upgrade DataEase to version 2.10.23 or later
- After upgrade, verify that SqlparserUtils.handleVariableDefaultValue() now properly escapes or parameterizes SQL variable defaultValue entries
- Confirm the upgrade was successful by checking the DataEase version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data