Daptin broken access control in YJS collaboration endpoint
Affects Daptin from 0.11.4 before 0.12.30 on deployments with at least one file.* typed column on a table. Fixed in 0.12.30.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 0.12.30
- Who is exposed
- Specific setups only
Summary
Daptin, a headless CMS, has a broken access control flaw in its generic YJS collaboration WebSocket endpoint, which does not check permissions on the database resource selected by a room name. A remote attacker with a low-privilege logged-in account can read or modify restricted row content without any user action.
Written by a model
Original description
Daptin is a GraphQL/JSON-API headless CMS. From 0.11.4 until 0.12.30, the generic GET /yjs/:documentName WebSocket route in InitializeYjsResources requires a session but does not authorize the database resource selected by a typename.referenceId.columnName room name. The YJS initial-content provider then reads the selected file.* column without CanRead or CanUpdate checks, and bidirectional synchronization allows a low-privileged authenticated user to read or modify restricted row content. Unauthenticated requests are rejected, and standalone non-canonical room names remain shared-by-name rooms. This issue is fixed in version 0.12.30.
What to do
Check whether your setup matches what the bug needs.
The deployment has at least one file.* typed column on a table.Upgrade to a fixed version: 0.12.30.
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-77369 (Daptin: Broken Access Control (IDOR) in the generic YJS collaboration endpoint), 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-77369 (entry last updated 2026-11-19):
Affected:
- daptin daptin: from 0.11.4, fixed in 0.12.30
Fixed versions: 0.12.30.
Conditions (all must be true for the bug to be hit):
- The deployment has at least one file.* typed column on a table. (source: https://github.com/daptin/daptin/security/advisories/GHSA-wj7x-58c2-5793)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-77369 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77369 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/daptin/daptin/security/advisories/GHSA-wj7x-58c2-5793
- https://github.com/daptin/daptin/commit/a1a3c48f88ce30632a57d3fe6a971033b23bd394
- https://github.com/daptin/daptin/releases/tag/v0.12.30
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-77369
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-77369"}.Affected versions
- daptin daptinFrom 0.11.4 · fixed in 0.12.30
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- GitHub PoC repos: 1
- Posted on X by cve.now Nov 19
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · daptin/daptin · Advisory GHSA-wj7x-58c2-5793 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77369 |
| Record | NVD · CVE-2026-77369 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-77369 · Repository |
| Other links 2 | |
| Repository | GitHub · daptin/daptin · Commit a1a3c48f |
| Repository | GitHub · daptin/daptin · Release v0.12.30 |
Questions about CVE-2026-77369
Is CVE-2026-77369 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
An authenticated low-privileged user can read the content of any file.* column on any row of any table, including admin-only tables. The same user can also push edits into that shared content.
Source: github.com
Which versions are affected by CVE-2026-77369?
daptin: from 0.11.4 before 0.12.30.
Source: cve.now feed data
Am I affected, and how do I check?
Daptin versions from 0.11.4 before 0.12.30 are in the affected range, but only deployments with at least one file.* typed column on a table are described as affected. To check, look at the Daptin version in use and at whether any table has a file.* typed column.
Source: github.com
How do I fix CVE-2026-77369?
Upgrade Daptin to 0.12.30, the fixed version in the affected range.
Source: github.com
Why do the sources disagree?
The description says the flaw can be reached without authentication, while the CVSS vector says PR:L, which means low privileges are required. The facts do not settle which of these is correct.
Source: github.com
Related
- CVE-2026-77367Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint
- CVE-2026-72575daptin - Authentication Bypass via Null Owner Permission Check on usergroup Objects
- CVE-2026-62160Daptin: ParseAcceptLanguage `_` separator bypass enables >250x CPU amplification via Accept-Language header in LanguageMiddleware
- CVE-2026-41422Daptin vulnerable to SQL injection via unvalidated goqu.L() calls in aggregate API
- CVE-2026-44349Daptin fuzzy search injects unvalidated column name into raw SQL
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
No corrections so far. Something wrong on this page? Report an error.