# CVE-2026-54443: Dashy: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

> Attackers can execute arbitrary JavaScript in the Dashy origin via malicious RSS feed links, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-2x3v-qmgm-r8hv

## What is CVE-2026-54443?

CVE-2026-54443 is a medium-severity cross-site scripting vulnerability in lissy93 dashy, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Dashy is a self-hostable personal dashboard. From 1.9.4 until 3.2.0, the Dashy RSS Widget in src/components/Widgets/RssFeed.vue does not sanitize RSS item link values before rendering feed item titles and Read More links as anchor href attributes, allowing an attacker-controlled feed to provide a javascript: URI that executes when clicked in the Dashy origin. This issue is fixed in version 3.2.0.

Weakness: CWE-84 (Improper Neutralization of Encoded URI Schemes in a Web Page), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2026-54443?


## How do I fix CVE-2026-54443?

No fix has been published for CVE-2026-54443 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54443 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54443 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54443 and fix it if it is affected.

What it is: CVE-2026-54443 is a medium-severity cross-site scripting vulnerability in lissy93 dashy, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54443 exists.

Affected product: lissy93 dashy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54443/ (Markdown: https://insights.sbomify.com/CVE-2026-54443/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54443
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54443
- OSV: https://osv.dev/vulnerability/CVE-2026-54443

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54443/
Summaries are generated and may contain mistakes; the official description above is the record.