dbcve.org
CWE-80Weakness · CWE-80

CVE-2026-54443

MEDIUM · 5.9 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable No privileges 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
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.

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 · high confidence

The Dashy RSS widget fails to sanitize RSS feed item link values before rendering them as anchor href attributes, allowing an attacker-controlled RSS feed to inject javascript: URIs that execute when users click on feed item links.

MitigationUpgrade Dashy to version 3.2.0 or later to obtain the patched code that properly sanitizes RSS feed links before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Dashy installation
    Locate the Dashy application instance in your environment. This may be running as a container, a Node.js service, or installed via your package manager. Identify the process or service running Dashy.
    Affected if Dashy is present in your environment
  2. Determine installed Dashy version
    Check the version of Dashy that is running. Common methods include: checking package.json in the application directory, querying the running container image tag, checking the application UI (often in About/Settings), or using CLI tools like 'docker ps' or 'npm list dashy'. Compare this version against 3.2.0.
    Affected if Dashy version is lower than 3.2.0
  3. Check if RSS widget is configured
    Examine your Dashy configuration file (commonly config.yml or through the UI dashboard) to determine if the RSS widget is enabled and has any feeds configured. Look for widget type 'rss' or similar RSS-related widget definitions.
    Affected if RSS widget is enabled and configured with one or more RSS feed URLs
  4. Inspect RSS feed sources
    Review the configured RSS feed URLs in the widget settings. Identify the source of each feed - whether it is a trusted internal feed or an external third-party feed. Malicious feeds can inject javascript: URIs into item links.
    Affected if Any configured RSS feed source is untrusted or external
  5. Verify widget rendering behavior
    If you have access to the running Dashy instance, add a test RSS feed with a known item containing a javascript: URI in the link field. Render the RSS widget and attempt to click the link to confirm whether the javascript: scheme executes or is blocked.
    Affected if javascript: URIs in RSS feed items are rendered as clickable links that execute JavaScript code

You are affected if running Dashy version older than 3.2.0 with the RSS widget enabled and configured to display feeds that may contain attacker-controlled links.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Dashy to version 3.2.0 or later to obtain the patched code that properly sanitizes RSS feed links before rendering.

Recommended fix High confidence

Dashy version 3.2.0

  1. 1. Backup your current Dashy installation and configuration
  2. 2. Upgrade Dashy to version 3.2.0 or later
  3. 3. Verify the upgrade was successful by checking the Dashy dashboard loads correctly
  4. 4. Test the RSS Widget functionality to ensure feeds render properly
Caveat Review release notes for any breaking changes between your current version and 3.2.0, particularly any configuration or feature changes

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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