dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-55633

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 →
93/100
Remediation priority · Urgent
Remotely reachable 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, a bypass of the H2 zip protocol and file dropper fix allows an authenticated attacker to upload a zip archive disguised with a .ttf extension through FontManage.saveFile and then exploit it through the zip protocol to achieve remote code execution. 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 before 2.10.24 allows authenticated attackers to bypass the H2 zip protocol and file dropper protections by uploading a malicious zip archive disguised with a .ttf extension through FontManage.saveFile, then exploiting it via the zip protocol to achieve remote code execution.

MitigationUpgrade to DataEase version 2.10.24 or later to apply the patch that fixes the zip protocol bypass and file upload validation.

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:H/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 installed DataEase version
    Access the DataEase administration panel or check the version file in the DataEase installation directory. The version is typically displayed in the UI footer or obtainable via API endpoint /api/sysInfo or config file.
    Affected if The installed version is earlier than 2.10.24.
  2. Verify FontManage.saveFile endpoint accessibility
    Review application permissions and role configurations to determine whether authenticated users (particularly non-admin users) have access to the FontManage.saveFile function. Check API access controls for /api/font/save or similar font management endpoints.
    Affected if Authenticated users with upload capabilities can access FontManage.saveFile without admin-level restrictions.
  3. Confirm zip protocol handling configuration
    Inspect DataEase security configuration files and H2 database settings to verify whether zip protocol handling is explicitly disabled or restricted in the application.
    Affected if Zip protocol handling is enabled or not explicitly blocked in the security configuration.
  4. Review file upload restrictions for font files
    Examine file upload validation settings to check if .ttf files are allowed to be uploaded through the FontManage.saveFile function, and whether uploaded files are stored in a web-accessible location.
    Affected if .ttf file uploads are permitted and stored in a location accessible via web requests.

Your environment is affected if DataEase version is below 2.10.24 and the FontManage.saveFile endpoint is accessible to authenticated users who can upload .ttf files that can then be accessed via zip protocol.

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 apply the patch that fixes the zip protocol bypass and file upload validation.

Recommended fix High confidence

2.10.24

  1. Back up your current DataEase installation and configuration
  2. Download DataEase version 2.10.24 from the official GitHub releases page: https://github.com/dataease/dataease/releases
  3. Stop the running DataEase service
  4. Upgrade or install DataEase to version 2.10.24 following standard upgrade procedures
  5. Start the DataEase service
  6. Verify the upgrade was successful by checking the version number and ensuring the service is running properly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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