CVE-2026-49867: DataEase: Authenticated Stored XSS in DataEase Template Static Resources
DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase template static resources let authenticated users submit TemplateManageRequest.staticResource through POST /de2api/templateManage/save or DataVisualizationServer.decompression, after which StaticResourceServer.saveFilesToServe and StaticResourceServer.saveSingleFileToServe write Base64-decoded .svg content to /de2api/static-resource/<name>.svg without validating extension, MIME type, decoded bytes, or SVG scriptability, causing stored same-origin cross-site scripting when a victim loads the resource. This issue is fixed in version 2.10.23.
Security readout for executives and security teams
Plain-English summary
CVE-2026-49867 is a stored cross-site scripting flaw in DataEase before 2.10.23. An authenticated user could store scriptable SVG content as a template static resource, causing same-origin script execution when another user loads it. This is business-relevant where DataEase is shared across teams or handles sensitive dashboards.
Executive priority
Prioritize remediation during the next normal security patch window, faster for multi-user or internet-accessible DataEase environments. The issue is not presented as actively exploited, but same-origin stored XSS can support account abuse and dashboard data exposure.
Technical view
DataEase accepted TemplateManageRequest.staticResource content through template save or decompression paths and wrote Base64-decoded SVG files under /de2api/static-resource/ without validating extension, MIME type, decoded bytes, or SVG scriptability. The vendor states version 2.10.23 fixes the issue.
Likely exposure
Exposure is limited to DataEase deployments running versions earlier than 2.10.23. Risk is higher where non-admin authenticated users can create, import, or manage templates and where privileged users regularly view shared template resources.
Exploitation context
The sources do not show active exploitation, and this CVE is not listed as KEV in the provided bundle. Exploitation requires an authenticated user and victim interaction: another user must load the stored same-origin resource.
Researcher notes
The advisory attributes the flaw to missing validation around stored SVG static resources. The provided evidence identifies the affected product, fixed version, vulnerable data path, and same-origin XSS impact, but does not include exploitation-in-the-wild evidence.
Mitigation direction
Upgrade DataEase to version 2.10.23 or later.
Review the DataEase advisory and release notes before deployment.
Restrict template creation and import privileges to trusted users.
Remove or review untrusted template static resources, especially SVG files.
Monitor DataEase activity for unusual template or static-resource changes.
Validation and detection
Inventory all DataEase instances and confirm their running versions.
Verify affected instances are upgraded to 2.10.23 or later.
Review roles allowed to save or import templates.
Check for recently added static resources from untrusted accounts.
Confirm vendor guidance is reflected in change-management records.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.