CVE
Hubleys Dashboard stored XSS via background image uploads
Affects the knrdl Hubleys dashboard before 0.5.2, where any authenticated non-admin user can upload a background image. Fixed in 0.5.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.5.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Any authenticated non-admin Hubleys user can upload a background image Background image upload feature is available to ordinary users
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Hubleys, a dashboard for self-hosted services from knrdl, has a stored cross-site scripting flaw: any logged-in non-admin user can upload a file as their background image and have it served with an attacker-chosen content type, so an embedded script can run without the app's Content-Security-Policy applying. The bug can be reached remotely by a user with a low-privilege account, and it is fixed in a patched release.
Read the original description
Hubleys is a dashboard for self-hosted services. Prior to version 0.5.2, any authenticated (non-admin) Hubleys user can upload a file with an arbitrary extension as their dashboard "background image," and the server will later serve that file back with a Content-Type derived straight from the attacker's chosen extension - so uploading an .html file gets it served as text/html. Because the endpoint that serves it returns a manually-constructed response rather than going through SvelteKit's normal page-rendering pipeline, the app's configured Content-Security-Policy never gets attached to it either, so a script embedded in the upload runs unrestricted. This issue has been patched in version 0.5.2.
Who should check
Teams running Hubleys dashboard up to 0.5.1 where regular non-admin users can log in and set background images.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Any authenticated non-admin Hubleys user can upload a background image Background image upload feature is available to ordinary usersUpgrade to a fixed version: 0.5.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-67444 (Hubleys: Stored XSS via unrestricted background-image upload, served with an attacker-chosen Content-Type and no CSP protection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-67444 (entry last updated 2026-11-13):
Affected:
- knrdl hubleys-dashboard: fixed in 0.5.2
Fixed versions: 0.5.2.
Conditions (all must be true for the bug to be hit):
- Any authenticated non-admin Hubleys user can upload a background image (source: https://github.com/knrdl/hubleys-dashboard/security/advisories/GHSA-j2w9-hhqw-mrq8)
- Background image upload feature is available to ordinary users (source: https://github.com/knrdl/hubleys-dashboard/security/advisories/GHSA-j2w9-hhqw-mrq8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-67444 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-67444 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/knrdl/hubleys-dashboard/security/advisories/GHSA-j2w9-hhqw-mrq8
- https://github.com/knrdl/hubleys-dashboard/commit/5a7f04c153295d48319d35fdd53e30f50288cd37
- https://github.com/knrdl/hubleys-dashboard/releases/tag/v0.5.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-67444
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-67444"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- knrdl hubleys-dashboard
fixed in 0.5.2
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-67444
Is CVE-2026-67444 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Uploaded background images are served with an attacker-chosen Content-Type and no CSP protection, so script in the uploaded file's link runs in the origin of anyone who opens it, including admins, and can act with the victim's privileges.Source: github.com, github.com
Which versions are affected by CVE-2026-67444?
hubleys-dashboard: before 0.5.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 0.5.2 are affected, and the feature is available to ordinary users because every user can change their own background image. To check a deployment, compare its Docker image tag ghcr.io/knrdl/hubleys-dashboard against 0.5.2.Source: github.com, github.com
How do I fix CVE-2026-67444?
Upgrade to version 0.5.2, for example the Docker image ghcr.io/knrdl/hubleys-dashboard:0.5.2.Source: github.com, github.com