Security readout for executives and security teams
Plain-English summary
SiYuan installations before version 3.7.4 may expose private document changes through their publishing interface. An unauthenticated observer could receive live edits, including content marked password-protected or forbidden. The issue threatens confidentiality rather than document integrity or availability.
Executive priority
Prioritize immediate remediation for internet-accessible or broadly reachable SiYuan instances below 3.7.4. The vulnerability can silently disclose sensitive live edits without credentials or user interaction. Although active exploitation is not established, the low attack complexity and severe confidentiality impact justify urgent inventory, upgrade, and exposure review.
Technical view
A missing authorization boundary in publish-surface WebSocket broadcast sessions allows anonymous clients to receive unfiltered real-time content events. The issue is classified as CWE-862 and scores 9.2 under CVSS 4.0, reflecting network-accessible, low-complexity disclosure with no privileges or user interaction required.
Likely exposure
Highest risk applies to SiYuan versions earlier than 3.7.4 where the publish surface and its WebSocket service are network-accessible. Potential impact rises when published workspaces contain sensitive, password-protected, or access-forbidden documents. The supplied sources do not establish whether every deployment exposes this interface by default.
Exploitation context
The described attack requires no authentication and can passively capture real-time edits through the publish surface. The bundle does not identify CVE-2026-72810 as being in KEV and provides no cited evidence of active exploitation. Public exploit availability and observed targeting are not established.
Researcher notes
The supplied record supports an authorization failure at the WebSocket broadcast boundary, but does not provide endpoint details, default exposure conditions, detection signatures, or evidence of exploitation. Validation should remain authorized and non-invasive. Investigators should distinguish ordinary publishing traffic from anonymous sessions capable of receiving protected content.
Mitigation direction
- Upgrade affected SiYuan installations to version 3.7.4 or later.
- Restrict network access to the publish surface until upgrades are complete.
- Review vendor guidance for any additional configuration or deployment-specific mitigations.
- Treat potentially exposed protected document content as sensitive and assess downstream response needs.
Validation and detection
- Inventory SiYuan instances and confirm their exact installed versions.
- Identify whether each publish surface and WebSocket service is reachable by untrusted networks.
- Review application and proxy logs for anonymous WebSocket connections to publishing interfaces.
- Confirm protected and forbidden documents are not delivered to unauthenticated publish sessions after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-72810 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-mw8r-mw84-88v2)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SiYuan before v3.7.4 Publish-Boundary Bypass via WebSocketCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.