CVE-2026-90529: DataEase stored XSS — LOW

CISO Take

A cross-site scripting flaw in DataEase's Symbolic Map chart component lets a low-privileged user inject malicious script through the tooltip backgroundColor attribute, which then executes in the browser session of anyone who views and interacts with the affected dashboard. The CVSS score is low (3.5) because exploitation requires an authenticated low-privilege account and victim interaction, there's no public exploit code or Nuclei template, it isn't in CISA KEV, and no EPSS score has been assigned — so mass exploitation is unlikely. The bigger concern is that the DataEase maintainers have been notified via a public issue tracker report and have not responded, meaning no patch timeline exists. If your organization uses DataEase to visualize AI/ML pipeline metrics or analytics for leadership, treat this as a session-hijacking risk against whoever has higher-privileged dashboard access, and mitigate by restricting chart-edit permissions, disabling public dashboard sharing, and applying a strict CSP until an official fix ships.

Sources: NVD

What is the risk?

Low overall risk. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N) requires an authenticated attacker with low privileges and depends on a victim interacting with the crafted chart, which limits blast radius and rules out unauthenticated mass exploitation. No EPSS score, no CISA KEV listing, no public exploit or scanner template exist, so there is no evidence of active or imminent exploitation. The main risk driver is not the technical severity but the lack of vendor response — DataEase was notified and has not acknowledged or patched the issue, so the exposure window is open-ended and organizations cannot rely on an upstream fix arriving soon.

How does the attack unfold?

Payload injection

A low-privileged DataEase user with chart-edit access sets a malicious script payload in the Symbolic Map tooltip's customAttr.tooltip.backgroundColor field and saves the chart.

AML.T0049

Victim interaction

A higher-privileged user opens the shared dashboard and interacts with the Symbolic Map, triggering the tooltip to render and execute the injected script in their browser session.

Session compromise and lateral impact

The script runs with the victim's privileges, allowing theft of their session token or execution of unauthorized DataEase actions, potentially exposing dashboards and analytics the low-privilege attacker could not otherwise access.

Payload injection

A low-privileged DataEase user with chart-edit access sets a malicious script payload in the Symbolic Map tooltip's customAttr.tooltip.backgroundColor field and saves the chart.

AML.T0049

Victim interaction

A higher-privileged user opens the shared dashboard and interacts with the Symbolic Map, triggering the tooltip to render and execute the injected script in their browser session.

Session compromise and lateral impact

The script runs with the victim's privileges, allowing theft of their session token or execution of unauthorized DataEase actions, potentially exposing dashboards and analytics the low-privilege attacker could not otherwise access.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
DataEase	—	—	No patch

Do you use DataEase? You're affected.

How severe is it?

CVSS 3.1

3.5 / 10

EPSS

0.2%

chance of exploitation in 30 days

Higher than 10% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AV Network

AC Low

PR Low

UI Required

S Unchanged

C None

I Low

A None

What should I do?

1 step

No official patch is available as of this analysis (vendor unresponsive per the public issue report github.com/dataease/dataease/issues/18846). Until a fix ships: (1) restrict chart creation/edit permissions to trusted users only, minimizing who can set customAttr.tooltip.backgroundColor values; (2) disable or tightly control public/shared dashboard links; (3) deploy a strict Content-Security-Policy on the DataEase frontend to reduce inline-script execution impact; (4) place DataEase behind a reverse proxy/WAF rule that strips script tags, event handlers, and javascript: URIs from chart configuration payloads; (5) monitor the upstream GitHub issue for a fix and upgrade promptly once released; (6) for detection, review DataEase audit logs for anomalous chart edits by low-privilege accounts and unexpected outbound requests from admin sessions.

How is it classified?

Code Execution Data Leakage Framework AML.T0049 - Exploit Public-Facing Application

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act

Article 15 - Accuracy, robustness and cybersecurity

ISO 42001

A.6.2.3 - AI system security

Frequently Asked Questions

What is CVE-2026-90529?

A cross-site scripting flaw in DataEase's Symbolic Map chart component lets a low-privileged user inject malicious script through the tooltip backgroundColor attribute, which then executes in the browser session of anyone who views and interacts with the affected dashboard. The CVSS score is low (3.5) because exploitation requires an authenticated low-privilege account and victim interaction, there's no public exploit code or Nuclei template, it isn't in CISA KEV, and no EPSS score has been assigned — so mass exploitation is unlikely. The bigger concern is that the DataEase maintainers have been notified via a public issue tracker report and have not responded, meaning no patch timeline exists. If your organization uses DataEase to visualize AI/ML pipeline metrics or analytics for leadership, treat this as a session-hijacking risk against whoever has higher-privileged dashboard access, and mitigate by restricting chart-edit permissions, disabling public dashboard sharing, and applying a strict CSP until an official fix ships.

Is CVE-2026-90529 actively exploited?

No confirmed active exploitation of CVE-2026-90529 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-90529?

No official patch is available as of this analysis (vendor unresponsive per the public issue report github.com/dataease/dataease/issues/18846). Until a fix ships: (1) restrict chart creation/edit permissions to trusted users only, minimizing who can set customAttr.tooltip.backgroundColor values; (2) disable or tightly control public/shared dashboard links; (3) deploy a strict Content-Security-Policy on the DataEase frontend to reduce inline-script execution impact; (4) place DataEase behind a reverse proxy/WAF rule that strips script tags, event handlers, and javascript: URIs from chart configuration payloads; (5) monitor the upstream GitHub issue for a fix and upgrade promptly once released; (6) for detection, review DataEase audit logs for anomalous chart edits by low-privilege accounts and unexpected outbound requests from admin sessions.

What systems are affected by CVE-2026-90529?

This vulnerability affects the following AI/ML architecture patterns: BI/analytics dashboards, ML monitoring dashboards, data visualization frontends.

What is the CVSS score for CVE-2026-90529?

CVE-2026-90529 has a CVSS v3.1 base score of 3.5 (LOW). The EPSS exploitation probability is 0.20%.

What is the AI security impact?

Affected AI Architectures

BI/analytics dashboardsML monitoring dashboardsdata visualization frontends

MITRE ATLAS Techniques

AML.T0049 Exploit Public-Facing Application

Compliance Controls Affected

EU AI Act: Article 15

ISO 42001: A.6.2.3

What are the technical details?

Original Advisory

A vulnerability has been found in DataEase up to 2.10.25/2.10.26. Affected by this issue is the function buildTooltip of the file core/core-frontend/src/views/chart/components/js/panel/charts/map/symbolic-map.ts of the component Symbolic Map. Such manipulation of the argument canvasViewInfo[*].customAttr.tooltip.backgroundColor leads to cross site scripting. The attack may be performed from remote. The project was informed of the problem early through an issue report but has not responded yet.

Exploitation Scenario

An attacker who has been granted a low-privilege DataEase account (e.g., a contractor or business user with chart-edit rights) creates or modifies a Symbolic Map chart and sets the customAttr.tooltip.backgroundColor field to a payload containing malicious JavaScript instead of a valid color value. The chart is saved to a shared dashboard. When a higher-privileged user — such as a DataEase administrator or an analyst reviewing AI/ML KPI dashboards — opens the dashboard and hovers over or interacts with the map (satisfying the UI:R requirement), the injected script executes in their authenticated browser session. The attacker uses this to exfiltrate the victim's session token or issue DataEase API calls on their behalf, potentially escalating privileges or accessing dashboards and datasets the low-privilege attacker could not otherwise view.

Weaknesses (CWE)

CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE-94 Improper Control of Generation of Code ('Code Injection')

CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'): The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
[Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.