CVE-2026-134450 in Dockhandinfo

Summary

by MITRE • 11/21/2026

Dockhand before 1.0.57 contains a clickjacking vulnerability because src/hooks.server.ts never sets X-Frame-Options or CSP frame-ancestors headers on responses. Attackers on a same-site origin can embed the UI in an invisible iframe to trick authenticated users into stopping stacks, deleting resources, or changing settings.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The identified vulnerability in Dockhand versions prior to 1.0.57 constitutes a classic clickjacking flaw rooted in insufficient security header configuration within the application server logic. Specifically, the file src/hooks.server.ts fails to implement critical protective headers such as X-Frame-Options or Content-Security-Policy with frame-ancestors directives on HTTP responses. This omission leaves the user interface vulnerable to being embedded within frames by external contexts without proper restrictions, allowing malicious actors to overlay invisible interactive elements atop legitimate application controls. The absence of these headers means that modern web browsers do not enforce any policy preventing the rendering of Dockhand content inside iframes, thereby creating an attack surface where visual deception can be effectively employed against authenticated users.

From a technical perspective, this vulnerability leverages the browser's default behavior regarding frame embedding when no explicit restrictions are present in the server response headers. An attacker hosting a malicious page on a same-site origin or potentially exploiting cross-origin scenarios depending on specific CORS configurations can construct an HTML document containing an iframe that loads the Dockhand interface at full opacity but with zero dimensions, effectively making it invisible to the end-user while remaining fully interactive. When an authenticated user visits this malicious site, their browser will load the Dockhand application within the hidden frame using their active session cookies and authentication tokens. The attacker can then position transparent or visually deceptive elements over critical UI components such as buttons for stopping stacks, deleting resources, or modifying system settings.

The operational impact of this vulnerability is significant due to its potential for unauthorized state changes and data destruction without direct user consent. Because the victim is authenticated, any actions performed within the hidden iframe are executed with full administrative privileges associated with that session. An attacker could trick a user into clicking what appears to be a benign element on their current webpage, which actually triggers an action in the background Dockhand instance. This could result in critical infrastructure disruption by stopping essential service stacks, permanent loss of data through resource deletion, or configuration drift caused by unauthorized setting changes. The stealth nature of this attack makes it particularly dangerous as victims may not realize they have interacted with a malicious overlay until damage has occurred.

This vulnerability aligns directly with CWE-1021 Improper Restriction of Rendered UI Layers or Frames and is categorized under the MITRE ATT&CK framework technique T1536 Single Event Dual Use, where an attacker uses legitimate functionality for unauthorized purposes through interface manipulation. To mitigate this risk, it is imperative to update Dockhand to version 1.0.57 or later which addresses these header omissions. In environments where immediate patching is not feasible, administrators should implement server-side middleware that explicitly sets the X-Frame-Options header to DENY or SAMEORIGIN and includes a Content-Security-Policy frame-ancestors directive restricted to trusted origins only. These measures ensure that browsers will refuse to render the application content within any unauthorized frames, thereby neutralizing the clickjacking attack vector entirely.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!