dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-45320

HIGH · 8.7 CVSS v4.0 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 5 weeks old

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 · unedited
DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase dashboard SQL variables such as ${deptId} are processed by SqlparserUtils.transFilter(), whose final branch returns raw user input for non-in and non-between operators before SubstitutedSql.replace("${var}", value) splices it into dashboard SQL, allowing authenticated users who can view a dashboard to inject SQL against integrated datasources. 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 confidence

In DataEase before version 2.10.23, dashboard SQL variables like ${deptId} are processed by SqlparserUtils.transFilter(), which has a code path that returns raw user input for non-IN and non-BETWEEN operators. This unsanitized input is then spliced directly into dashboard SQL queries via SubstitutedSql.replace(), allowing authenticated users who can view dashboards to perform SQL injection attacks against integrated datasources.

MitigationUpgrade DataEase to version 2.10.23 or later. If immediate upgrade is not feasible, implement input validation and parameterized queries in SqlparserUtils.transFilter() to prevent raw user input from reaching SQL execution.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify DataEase version
    Check the installed DataEase version by accessing the admin panel, checking the build metadata, or running: docker images | grep dataease (for containerized deployments). Compare against version 2.10.23.
    Affected if The installed version is prior to 2.10.23
  2. Locate dashboards using SQL variables
    Review dashboard configurations for the presence of SQL variable syntax such as ${deptId}, ${userId}, or other ${variableName} patterns used in SQL queries.
    Affected if Dashboards contain SQL variables that reference user-controlled or dynamic values
  3. Identify non-IN and non-BETWEEN operators in variable usage
    Inspect dashboard SQL queries that use variables and check if the variable is used with operators other than IN or BETWEEN (for example: =, <>, >, <, LIKE, etc.).
    Affected if SQL variables are used with operators other than IN or BETWEEN, allowing raw input to be spliced into queries
  4. Verify authentication requirements for dashboards
    Check the access control settings for dashboards that use SQL variables. Determine if unauthenticated or low-privilege users can view these dashboards.
    Affected if Authenticated users with limited privileges can view dashboards containing vulnerable SQL variable patterns

You are affected if running DataEase version prior to 2.10.23 AND you have dashboards using SQL variables with non-IN/BETWEEN operators accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade DataEase to version 2.10.23 or later. If immediate upgrade is not feasible, implement input validation and parameterized queries in SqlparserUtils.transFilter() to prevent raw user input from reaching SQL execution.

Recommended fix Moderate confidence

2.10.23

  1. 1. Backup the current DataEase installation and database
  2. 2. Download DataEase version 2.10.23 from the official GitHub repository releases
  3. 3. Stop the running DataEase service
  4. 4. Upgrade the installation following the standard DataEase upgrade procedure
  5. 5. Verify the upgrade was successful by checking the version number
  6. 6. Test that dashboard SQL variables function correctly after the upgrade
Caveat Review release notes between your current version and 2.10.23 for any potential breaking changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45320 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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