dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-45419

HIGH · 8.5 CVSS v4.0 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
91/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 template saves call TemplateManageService#save, StaticResourceServer#saveFilesToServe, and the /de2api/templateManage/save endpoint with attacker-controlled staticResource names and Base64 content, allowing path traversal and arbitrary file writes because only / was used when extracting the file name. 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

DataEase versions prior to 2.10.23 contain a path traversal vulnerability in the template save functionality (TemplateManageService#save, StaticResourceServer#saveFilesToServe, and /de2api/templateManage/save). Attackers can manipulate staticResource names containing path traversal sequences (e.g., '../') combined with Base64-encoded content to write arbitrary files to the filesystem outside the intended directory, because the code only used '/' when extracting filenames without proper sanitization.

MitigationUpgrade DataEase to version 2.10.23 or later to obtain the patch that properly validates and extracts file names, preventing path traversal and arbitrary file writes.

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:N/VI:H/VA:H/SC:N/SI:H/SA:H/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 and version
    Locate the DataEase installation directory and check for version indicators such as a version file, build properties, or query the application health/API endpoint that returns version information
    Affected if The installed version is lower than 2.10.23 (e.g., 2.10.0 through 2.10.22) or if the version cannot be determined and the product is DataEase
  2. Verify template management API is accessible
    Check if the /de2api/templateManage/save endpoint is exposed and reachable in the DataEase deployment (typically at the application's base URL)
    Affected if The endpoint responds and accepts requests, indicating the template save functionality is available
  3. Confirm static resource handling is enabled
    Inspect whether the StaticResourceServer component and template save functionality are loaded and operational in the running DataEase instance
    Affected if The static resource upload/save feature is enabled and accessible to users or administrators

A DataEase installation is affected if it is version 2.10.22 or earlier and has the template save API (/de2api/templateManage/save) accessible, allowing path traversal via '../' sequences in staticResource names to write files outside the intended directory.

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 to obtain the patch that properly validates and extracts file names, preventing path traversal and arbitrary file writes.

Recommended fix High confidence

DataEase 2.10.23

  1. 1. Back up your current DataEase installation and database.
  2. 2. Download DataEase version 2.10.23 from the official GitHub repository.
  3. 3. Stop the running DataEase service.
  4. 4. Install or upgrade to version 2.10.23 following the standard DataEase upgrade procedures.
  5. 5. Verify the installation by checking that the /de2api/templateManage/save endpoint is accessible and functioning correctly.
  6. 6. Confirm the path traversal vulnerability is resolved by testing that file saves are restricted to allowed directories.
  7. 7. Restart the DataEase service.
  8. 8. Monitor logs for any unusual file access attempts.
Caveat Review release notes for any configuration or feature changes between your current version and 2.10.23

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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