Quick answers
- Is CVE-2026-45419 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45419 being exploited in the wild.
- How severe is CVE-2026-45419?
- Informational severity, with a CVSS score of 8.5, published 15 July 2026.
- Which products and versions are affected?
- DataEase < 2.10.23.
- Is there a fix for CVE-2026-45419?
- A patch was published on 2026-05-28: Version 2.10.23 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45419 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45419?
- Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in DataEase prior to version 2.10.23 within the `TemplateManageService#save` and `StaticResourceServer#saveFilesToServe` methods. The `/de2api/templateManage/save` endpoint accepts a `staticResource` parameter containing Base64-encoded content and a filename. The application incorrectly extracts the filename by only searching for the forward slash (`/`) character, failing to account for backslashes (`\`) or directory traversal sequences (`../`). An authenticated attacker can provide a crafted path (e.g., using `..\..\`) to write arbitrary files outside of the intended directory. This can be leveraged to overwrite critical system files or achieve remote code execution. The issue is resolved in version 2.10.23 by implementing proper filename extraction and validation.
Affected products
- DataEase DataEase < 2.10.23
Timeline
- 2026-05-28: patched: Version 2.10.23 released
- 2026-05-28: advisory: GitHub Security Advisory GHSA-83fh-fgh3-g9f9 published
- 2026-07-15: disclosed: CVE-2026-45419 published to NVD