dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-53729

HIGH · 8.7 CVSS v4.0 Published 2026-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 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.24, any authenticated user can download (/exportCenter/download/{id}), delete (/exportCenter/delete), retry (/exportCenter/retry/{id}), or generate download links (/exportCenter/generateDownloadUri/{id}) for export tasks belonging to other users by manipulating the task ID parameter, and the /exportCenter/download/{id} endpoint is whitelisted from authentication, allowing unauthenticated access to exported files. This issue is fixed in version 2.10.24.

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

DataEase versions prior to 2.10.24 contain two distinct vulnerabilities: (1) an Insecure Direct Object Reference (IDOR) allowing any authenticated user to manipulate task ID parameters to access, delete, retry, or generate download links for other users' export tasks, and (2) an authentication bypass where the /exportCenter/download/{id} endpoint is whitelisted, permitting unauthenticated access to exported files.

MitigationUpgrade to DataEase version 2.10.24 or later to obtain the vendor fix; immediately review export task access logs for unauthorized activity and consider temporarily restricting the download endpoint if immediate patching is not feasible.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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 installation
    Locate DataEase service in your environment. Look for processes named 'dataease', Docker containers with 'dataease' in the name, or services running on default DataEase ports (commonly 8080).
    Affected if DataEase is installed and running in the environment
  2. Determine installed DataEase version
    Check the DataEase version. This is typically accessible via the admin panel under 'About' or by querying the API endpoint /api/sysInfo. Compare your version to the affected range: any version prior to 2.10.24.
    Affected if Installed version is below 2.10.24
  3. Verify export center is accessible
    Confirm the export center functionality exists and is enabled. Attempt to access or query the /exportCenter/ API endpoints, or check if export features appear in the DataEase user interface.
    Affected if Export center module is enabled and accessible to users
  4. Test download endpoint authentication
    Attempt to access the /exportCenter/download/{id} endpoint using an unauthenticated request (no session cookie or token). Use a tool like curl: curl -v https://your-dataease-host/exportCenter/download/1
    Affected if The endpoint returns file content or a valid download response without requiring authentication

Your environment is affected if DataEase version is below 2.10.24 and the export center module is enabled, which would allow unauthenticated access to other users' exported files via the download endpoint.

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 to DataEase version 2.10.24 or later to obtain the vendor fix; immediately review export task access logs for unauthorized activity and consider temporarily restricting the download endpoint if immediate patching is not feasible.

Recommended fix High confidence

2.10.24

  1. Upgrade DataEase to version 2.10.24 or later to remediate this vulnerability.
  2. In version 2.10.24, the IDOR vulnerability in /exportCenter/download/{id}, /exportCenter/delete, /exportCenter/retry/{id}, and /exportCenter/generateDownloadUri/{id} endpoints has been fixed.
  3. After upgrading, verify that users can no longer access export tasks belonging to other users by manipulating task IDs.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53729 — 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-53729 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