Security readout for executives and security teams
Plain-English summary
DataEase before 2.10.23 can let a logged-in attacker write files outside the intended template resource area. That can damage application integrity and availability, and may enable broader compromise depending on where files can be written.
Executive priority
Treat as high priority for DataEase environments. Patch promptly because exploitation requires only low privileges and can alter or disrupt server-side files.
Technical view
The vulnerable template save flow reaches TemplateManageService#save, StaticResourceServer#saveFilesToServe, and /de2api/templateManage/save with attacker-controlled staticResource names and Base64 content. Insufficient path handling, categorized as CWE-22, allows path traversal and arbitrary file writes. Fixed in 2.10.23.
Likely exposure
Organizations running DataEase versions earlier than 2.10.23 are exposed, especially where low-privileged authenticated users can access template management functionality over the network.
Exploitation context
The CVSS vector indicates network access, low privileges, no user interaction, and high integrity and availability impact. The provided sources do not show KEV listing or confirmed active exploitation.
Researcher notes
The key weakness is filename/path extraction that only handled /, allowing traversal through staticResource names. Evidence supports arbitrary file write before 2.10.23, but does not establish exploitation in the wild.
Mitigation direction
- Upgrade DataEase to version 2.10.23 or later.
- Review the GitHub advisory and release notes before rollout.
- Inventory DataEase instances and identify versions below 2.10.23.
- Restrict template management access to trusted users until patched.
- Monitor for unexpected file changes in DataEase service directories.
Validation and detection
- Confirm each DataEase instance version is 2.10.23 or later.
- Check whether template management is reachable by low-privileged users.
- Review logs for /de2api/templateManage/save activity.
- Inspect recent template static resources for suspicious file paths.
- Verify patch deployment through package, container, or release metadata.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45419 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dataease/dataease/security/advisories/GHSA-83fh-fgh3-g9f9CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/dataease/dataease/commit/d34f413ef047bd275909d67310d200cbc8ae31baCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/dataease/dataease/releases/tag/v2.10.23CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.