External risk intelligence

Daptin Authentication Bypass Allows Unauthorized Data Access and Modification.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-77369

The vulnerability exists in a headless CMS, which is typically deployed as a web-facing API service. While the issue specifically affects authenticated users, headless CMS platforms and their associated WebSocket-based synchronization endpoints are commonly exposed to the public internet to facilitate content management and application connectivity.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the Daptin headless CMS, affecting how authenticated users access and synchronize data. This issue could allow a low-privileged user to read or modify restricted content, potentially impacting the integrity of stored information. The main concern is to confirm if this technology is in use and assess any exposure.

  • Allows authenticated users to change restricted data.
  • Impacts data integrity in Daptin CMS.
  • Confirm relevance and exposure of Daptin.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by leveraging their existing low-privileged access within the Daptin system. They would target a specific WebSocket route that handles Yjs document synchronization. By manipulating the request to reference a protected database column, the attacker can bypass authorization checks and gain the ability to read or alter restricted data.

  • Requires authenticated user access.
  • Triggers via a specific WebSocket route.
  • Risks unauthorized data access and modification.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a low-privileged authenticated user to read or modify restricted row content within the Daptin headless CMS by exploiting weaknesses in the WebSocket route's authorization checks. Unauthenticated requests are not affected, and the vulnerability does not impact standalone non-canonical room names.

  • Restricted row content could be accessed.
  • Low-privileged users could bypass checks.
  • Data could be read or modified.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and potentially platform or infrastructure teams are likely responsible for addressing this critical vulnerability in Daptin. The first practical move is to identify all Daptin deployments, confirm their reachability and business criticality, and then engage the accountable owners to plan remediation.

  • Application owners should manage the issue.
  • Verify Daptin instances and exposure first.
  • Plan coordinated remediation with owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Daptin?

Daptin is a headless Content Management System (CMS) that exposes GraphQL and JSON-APIs. It is designed to manage database content through web-based interfaces, often relying on WebSocket connections for real-time synchronization of data across connected clients.

What does CVE-2026-77369 mean for security?

This vulnerability involves missing authorization checks, technically categorized under CWE-639 (Authorization Bypass Through User-Controlled Key) and related weaknesses. Essentially, the system fails to verify if a user has permission to access or change a specific database record, allowing them to interact with data they should not be able to see or edit.

How can an attacker trigger this vulnerability?

An attacker needs an existing low-privileged account to interact with the specific WebSocket route used for Yjs document synchronization. Requests from unauthenticated users are rejected by the system, and the bug does not affect standalone non-canonical room names, which are not linked to the restricted database resources.

Is my Daptin instance relevant to this risk?

According to Halo Surface Signal, this vulnerability is highly relevant for web-facing deployments. Because headless CMS platforms like Daptin are frequently exposed to the public internet to enable application connectivity and content management, instances accessible from the outside are the primary concern for unauthorized access.

What should I do if I use Daptin?

First, conduct an inventory to identify all Daptin deployments within your environment and determine their network accessibility. Once identified, coordinate with the application owners to update your software to version 0.12.30 or later, which contains the necessary patches to enforce proper authorization checks.

References