dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-55647

MEDIUM · 5.1 CVSS v4.0 Published 2026-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
55/100
Remediation priority · Elevated
Remotely reachable Patch available 6 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.24, dashboard text components render stored component content with Vue v-html without server-side HTML sanitization, allowing an authenticated user who can edit dashboard component data to inject HTML with executable event handlers that execute when another user or shared-link visitor views the dashboard. This issue is fixed in version 2.10.24.

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:L/SI:L/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

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 →
Recommended fix High confidence

2.10.24

  1. 1. Back up the current DataEase installation and database before proceeding with any upgrade.
  2. 2. Review the DataEase upgrade documentation for your current version to ensure compatibility with version 2.10.24.
  3. 3. Upgrade DataEase to version 2.10.24 or later by following the official upgrade instructions.
  4. 4. After upgrade, verify that the dashboard text component properly sanitizes HTML content.
  5. 5. Test that existing dashboards render text components correctly without executable event handlers.
  6. 6. Confirm that the fix (commit 9565812980da781eda04c0a3632bf5dc8b0469f6) is included in the upgraded version.
Caveat Review release notes for any configuration or feature changes between your current version and 2.10.24

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

We can apply and verify the patch for your build — typical engagement from $900. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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