Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify internet-exposed SiYuan publish endpoint
-
DeliverySend unauthenticated HTTP GET to affected API path (search/graph/backlink/tags)
-
ExploitAuthorization check applies visibility list instead of disabled list
-
ExecutionReceive forbidden document content in API response
-
ImpactExfiltrate sensitive notes and relationship data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target SiYuan instance has publish mode explicitly enabled and is reachable over the network by the attacker. The authorization flaw exists only in the eight publish-mode reader-facing endpoints; SiYuan installations operating without publish mode are not exposed through this vulnerability. No authentication is required (CVSS PR:N confirmed), and no user interaction is needed. Exploitation is meaningful only when at least one document has been placed on the disabled list - installations where no content has been restricted via the disabled list have no forbidden material to leak. The key limiting factors for defenders are therefore: publish mode must be on, the instance must be network-accessible, and the operator must have used the disabled-list feature to restrict specific documents. |
| Impact | The CVSS 4.0 base score of 8.7 with vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H accurately reflects the severity: the flaw is trivially exploitable over the network by any unauthenticated party, with no attack complexity and high confidentiality impact against the vulnerable system. Even a mid-sized municipal IT team in kielce running SiYuan as a publish-mode knowledge base accessible from the public internet should treat this as urgent, since the disabled-list mechanism they rely on to protect sensitive content provides no actual protection on any of the eight affected endpoints. No EPSS score was supplied in the input data, and the vulnerability does not appear in the CISA KEV catalog, so active exploitation in the wild is not confirmed. The attack requires no specialized tooling - standard HTTP GET requests to well-known publish API paths suffice - making exploitation highly automatable once endpoint naming conventions are known, which is a meaningful escalation of real-world risk beyond the theoretical CVSS signal. The primary mitigating factor is the deployment precondition: only SiYuan instances running in publish mode with internet exposure are affected, which reduces the exposed population relative to the full install base. |
| Exploit ScenarioDerived | An unauthenticated remote attacker identifies an internet-exposed SiYuan instance running in publish mode by probing known publish-API endpoint paths. The attacker sends a standard HTTP GET request to the search or recent-documents endpoint and receives a response containing notes the operator explicitly marked as forbidden from publishing - potentially revealing private research, internal project documentation, or sensitive personal information embedded in the knowledge graph. No proof-of-concept code is publicly known at time of analysis, but the exploit requires only curl or a browser and knowledge of the SiYuan publish API path structure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
Publish-mode endpoint misconfiguration in SiYuan before v3.7.4 exposes operator-forbidden documents to anonymous remote visitors. Eight reader-facing API endpoints - covering search, backlinks, asset content, saved criteria, recent documents, graph, and tags - incorrectly apply the visibility access-control list rather than the disabled list, bypassing the intended publication restriction. Unauthenticated attackers can enumerate and read content that the SiYuan operator has explicitly marked as forbidden from publishing; no public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
RemediationAI
Upgrade SiYuan to v3.7.4 or later, which corrects the authorization logic on all eight affected endpoints to apply the disabled list rather than the visibility list (vendor advisory: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-48p5-pffc-5r9p). If an immediate upgrade is not possible, disabling publish mode entirely removes the attack surface at the cost of all external publishing capability - this is the most effective interim control. Operators who cannot disable publish mode should restrict network access to the SiYuan instance at the reverse-proxy or firewall layer, permitting only trusted IP ranges to reach the publish API; this prevents remote unauthenticated access but does not fix the underlying authorization flaw and prevents legitimate public readers from accessing any published content. A more surgical approach is to configure the reverse proxy to block the specific vulnerable endpoint paths under the publish API namespace, though this requires enumerating the full path surface and carries ongoing maintenance risk as the application evolves.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SiYuan (cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:*) is a self-hosted, privacy-first personal knowledge management system that includes a publish mode allowing selective external exposure of notes. The access-control model distinguishes between a visibility list (controls which documents appear in navigation) and a disabled list (controls which documents are forbidden from publishing). CWE-863 (Incorrect Authorization) precisely describes the root cause: the server-side authorization logic on eight reader-facing endpoints references the wrong list, meaning documents forbidden via the disabled list are still evaluated against the more permissive visibility list and returned to anonymous callers. The affected endpoints span the core discovery surface of the publish API - search, backlink traversal, asset content retrieval, saved search criteria, recent document history, graph relationships, and tag indexes - meaning the full content graph of forbidden documents is reachable, not just their titles.
Know when Siyuan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Network-accessible with no credentials or user interaction required; impact is confidentiality-only as forbidden documents are read but not modified or deleted.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
SiYuan before v3.7.4 contains an incorrect authorization vulnerability in eight publish-mode reader-facing endpoints that filter results using the visibility list instead of the disabled list. Anonymous visitors can discover and read content from documents explicitly marked as forbidden from publishing by accessing search, backlink, asset content, saved criteria, recent documents, graph, and tag endpoints.
Executive ViewAI
SiYuan knowledge management systems before version 3.7.4 contain an access-control misconfiguration that allows unauthenticated attackers to read and enumerate documents the operator has explicitly marked as forbidden from publication. Organizations using affected versions face uncontrolled exposure of internal knowledge base content to anonymous internet users. Immediate action is required to either upgrade to patched versions or implement interim access controls, particularly for deployments containing confidential materials.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to affected endpoints using reverse-proxy authentication, IP whitelisting, or mandatory API key requirements; consider air-gapping or disabling SiYuan instances containing sensitive materials until v3.7.4 or later is deployed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
SQL injection in SiYuan's fullTextSearchAssetContent endpoint lets unauthenticated attackers and holders of publish Role
Stored cross-site scripting in SiYuan personal knowledge management before 3.7.0 lets an attacker with write access to a
SQL injection in SiYuan personal knowledge management (versions <= v3.7.2) lets attackers pass arbitrary SQL statements
Stored cross-site scripting in SiYuan's attribute-view (database) cell renderer, affecting all versions prior to 3.7.0,
SQL injection in SiYuan personal knowledge-management software (all versions before v3.7.3) lets attackers inject arbitr
A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems. Rated critical severity (CVSS 9.8), t
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the ids array parameter in /batchGetBlockAttrs. R
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the id parameter at /getAssetContent. Rated criti
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the notebook parameter in /searchHistory. Rated c
SiYuan personal knowledge management system prior to 3.5.4 has a stored XSS vulnerability (CVSS 9.6) that allows code ex
Remote code execution in SiYuan note-taking application (before v3.6.1) allows any malicious Bazaar marketplace package
Origin-validation bypass in SiYuan Note (open-source personal knowledge management) before 3.7.0 lets any installed Chro
EUVD-2026-60587
GHSA-x3p9-xqgm-hxww
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB