Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55592 – Reflected XSS – Dashy ≤ 4.3.6

Be the first to know when new zero-days emerge:

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 /workspace endpoint accepts a url query parameter and renders it as the src attribute of an embedded iframe without validating or sanitising the URI scheme. This allows javascript: 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge