Security readout for executives and security teams
Plain-English summary
SiYuan before v3.7.4 can expose content that users believed was protected by a publishing password. An unauthenticated remote party may retrieve document blocks and their reference relationships through two graph endpoints. The issue affects confidentiality rather than integrity or availability.
Executive priority
Prioritize immediate remediation for internet-facing or broadly accessible instances containing sensitive protected documents. The flaw defeats an intended confidentiality control without requiring credentials. Internal-only instances should still be inventoried and upgraded promptly based on content sensitivity and network reachability.
Technical view
The getGraph and getLocalGraph endpoints do not enforce the publish-password authorization tier in affected versions. Network-accessible, unauthenticated requests can therefore retrieve block-level content from password-protected documents and disclose the complete reference topology. The issue is classified as CWE-200 with CVSS 4.0 score 9.2.
Likely exposure
Exposure is most likely where SiYuan earlier than v3.7.4 publishes password-protected documents and the affected graph endpoints are reachable by untrusted users. Instances without affected versions, protected published content, or network reachability are less likely to be exposed.
Exploitation context
Exploitation requires network access but no privileges, user interaction, or password, according to the supplied CVSS vector and description. The bundle does not identify CISA KEV listing or provide evidence of active exploitation. Public technical advisories may nevertheless increase discovery and probing risk.
Researcher notes
The supplied affected range is represented ambiguously as versions “0” and “3.7.4,” while the title and description consistently state versions before v3.7.4. Validate exact version-range semantics against the vendor advisory. Available evidence supports confidentiality impact only; it does not establish modification, service disruption, or exploitation in the wild.
Mitigation direction
- Upgrade affected SiYuan instances to v3.7.4 or later.
- Until upgraded, restrict untrusted network access to affected SiYuan publishing interfaces.
- Review vendor guidance for any additional configuration or containment recommendations.
- Treat exposed protected-document content as potentially disclosed and follow internal incident procedures.
Validation and detection
- Inventory SiYuan instances and confirm their installed versions.
- Identify instances publishing password-protected documents to network-accessible users.
- Confirm anonymous access to protected graph content is rejected after remediation.
- Review access logs for unexpected requests to getGraph and getLocalGraph.
- Assess whether potentially exposed documents contain sensitive or regulated information.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-72804 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-vpjw-wf5h-cgpq)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SiYuan before v3.7.4 Authentication Bypass via Graph EndpointsCVE 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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.