Summary
CVE-2026-55592 is a Reflected Cross-Site Scripting (XSS) vulnerability affecting Dashy, a self-hosted web dashboard application, in all versions up to and including 4.3.6. The flaw resides in the Workspace component, where the url query parameter is passed directly to an iframe src attribute without scheme validation, enabling injection of javascript: URIs. With a CVSS v3.1 score of 6.1 (Medium), successful exploitation requires no authentication and allows an attacker to execute arbitrary JavaScript within the victim’s browser in the context of the Dashy origin.
Technical details
- Root cause: The
/workspaceendpoint accepts aurlquery parameter and renders it as thesrcattribute of an embedded iframe without validating or sanitising the URI scheme. This allowsjavascript:URIs to pass unchecked. - Trigger condition: An attacker crafts a malicious URL (e.g.
/workspace?url=javascript:alert(document.domain)) and delivers it to a victim who opens the link while their browser is pointed at the vulnerable Dashy instance. - Attack vector: Network-based; no credentials or prior access to the target instance are required. The attack requires victim interaction (the victim must follow the crafted URL).
- Impact: Arbitrary JavaScript execution within the Dashy origin. Consequences include session token theft, DOM manipulation, credential harvesting from autofill or stored data, and the ability to make authenticated requests to Dashy on the victim’s behalf — which may expose links to internal services, API keys, and infrastructure information stored in the dashboard.
Affected software
- Dashy (lissy93/dashy) — all versions ≤ 4.3.6
Severity
- CVSS v3.1 Base Score: 6.1 (Medium)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - CWE: CWE-79 – Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
Mitigation and recommended actions
- Immediate action: Upgrade Dashy to version 4.3.7 or later, which contains the vendor fix for this vulnerability.
- If patching is not immediately possible:
- Restrict public internet access to Dashy instances; place the dashboard behind a VPN or authenticated reverse proxy to eliminate the attack surface.
- Enforce strict Content Security Policy (CSP) headers at the reverse proxy or web server level to block
javascript:URI execution as an additional defensive layer.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

