CVE-2026-67444: Hubleys: Stored XSS via unrestricted background-image upload, served with an attacker-chosen Content-Type and no CSP protection

Published Nov 13, 2026
·
Updated

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.

Affected Software

1 affected component
Hubleys<0.5.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.5.2

Event History

Nov 13, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any authenticated Hubleys user, including a non-admin user, can upload a malicious file as their dashboard background image. Exploitation therefore requires an account rather than unauthenticated access.

2

What must an attacker do to trigger script execution?

The attacker uploads a file such as an .html file as a background image, causing it to be served as text/html. A victim must later load the uploaded file for the embedded script to execute.

3

Are default CSP protections effective for the uploaded file endpoint?

No. The file-serving endpoint constructs its response manually and does not attach Hubleys' configured Content-Security-Policy, so scripts in an uploaded HTML file can run without that CSP protection.

4

Which versions are affected, and what version fixes the issue?

Versions prior to 0.5.2 are affected. The issue is patched in Hubleys version 0.5.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203