CVE-2026-49867
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 · uneditedDataEase 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.
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 confidenceDataEase allows authenticated users to upload Base64-decoded SVG files through the template management API endpoints (/de2api/templateManage/save and DataVisualizationServer.decompression) without validating the file extension, MIME type, decoded content, or SVG scriptability. The uploaded files are stored to /de2api/static-resource/<name>.svg and served to other users, enabling stored same-origin cross-site scripting (XSS) when victims access the malicious SVG.
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
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:H/SI:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed DataEase versionCheck the DataEase application version through its web interface (typically in About or Settings) or by querying the application's API/version endpoint. Compare this version number against 2.10.23.Affected if The installed version is lower than 2.10.23 (e.g., 2.10.0 through 2.10.22).
-
Confirm API endpoint exposureVerify that the endpoints /de2api/templateManage/save and the DataVisualizationServer.decompression method are accessible on the server. This can be done by attempting to access these paths via HTTP GET or POST requests from an authenticated session.Affected if These API endpoints are reachable and accept requests without additional security controls.
-
Examine static resource directory for SVG filesInspect the /de2api/static-resource/ directory on the web server (if accessible) or review uploaded template files. Look for any .svg files present in this location.Affected if SVG files exist in /de2api/static-resource/ that were uploaded by users.
-
Analyze SVG file contents for script elementsOpen and review the content of any SVG files found in the static-resource directory. Specifically look for <script> tags, javascript: URIs, event handler attributes (onclick, onload, etc.), or embedded executable content.Affected if Any SVG file contains script elements, javascript: handlers, or other scriptable content (SVG with <script>, event handlers, or embedded objects).
-
Check if SVG files are being served to usersVerify that SVG files from /de2api/static-resource/ are accessible via web browser to other users (not just the uploader). Attempt to access a known SVG file URL from an incognito or different authenticated session.Affected if SVG files are served to other users without sanitization, allowing the XSS payload to execute in their browsers.
You are affected if DataEase version is below 2.10.23 AND the application serves uploaded SVG files from /de2api/static-resource/ that contain scriptable content.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to DataEase version 2.10.23 or later, which includes proper validation of file extensions, MIME types, and SVG content sanitization. If immediate upgrade is not possible, restrict access to the affected API endpoints and implement input validation to reject SVG files containing script elements.
2.10.23
- 1. Backup your current DataEase installation and database before upgrading.
- 2. Stop the DataEase service to prevent any active sessions during the upgrade.
- 3. Download DataEase version 2.10.23 from the official GitHub releases page (github.com/dataease/dataease).
- 4. Follow the standard DataEase upgrade procedure for your deployment method (Docker, Kubernetes, or direct installation).
- 5. Start the DataEase service and verify it is running correctly.
- 6. Confirm the upgrade to version 2.10.23 by checking the About or version information in the DataEase admin panel.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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