CVE-2026-30926: CWE-284: Improper Access Control in siyuan-note siyuan
SiYuan is a personal knowledge management system. Prior to 3.5.10, a privilege escalation vulnerability exists in the publish service of SiYuan Note that allows low-privilege publish accounts (RoleReader) to modify notebook content via the /api/block/appendHeadingChildren API endpoint. The endpoint requires only the model.CheckAuth role, which accepts RoleReader sessions, but it does not enforce stricter checks, such as CheckAdminRole or CheckReadonly. This allows remote authenticated publish users with read-only privileges to append new blocks to existing documents, compromising the integrity of stored notes.
AI Analysis
Technical Summary
SiYuan Note is a personal knowledge management system used for organizing and storing notes. In versions prior to 3.5.10, a critical access control vulnerability (CVE-2026-30926) exists in its publish service, specifically in the /api/block/appendHeadingChildren API endpoint. This endpoint is intended to allow users to append heading children blocks to notebooks. However, it only enforces a minimal authorization check (model.CheckAuth), which permits sessions with RoleReader privileges—intended as read-only access—to perform this action. The lack of stricter role enforcement such as CheckAdminRole or CheckReadonly means that users with read-only publish accounts can escalate their privileges to modify notebook content. This improper access control (CWE-284) and authorization bypass (CWE-862) flaw compromises the integrity of stored notes by allowing unauthorized content modification. The vulnerability is remotely exploitable by authenticated users without requiring user interaction beyond authentication. The CVSS v3.1 score of 7.1 reflects a high severity due to low attack complexity, network attack vector, and significant impact on integrity, though confidentiality and availability impacts are limited. No public exploits have been reported yet, but the vulnerability poses a serious risk to the integrity of knowledge assets managed by SiYuan Note users.
Potential Impact
The primary impact of this vulnerability is the compromise of data integrity within SiYuan Note notebooks. Unauthorized users with read-only publish accounts can append or modify content, potentially injecting misleading, malicious, or erroneous information. This can undermine trust in the knowledge management system, disrupt workflows, and cause misinformation to propagate within organizations. Since SiYuan Note is used for personal and collaborative knowledge management, the integrity breach could affect decision-making, documentation accuracy, and intellectual property. Although confidentiality and availability are not directly impacted, the ability to alter stored content without proper authorization represents a significant risk. Organizations relying on SiYuan Note for critical documentation or collaborative knowledge sharing are at risk of data tampering, which could have downstream effects on operational security and compliance. The vulnerability is exploitable remotely by authenticated users, increasing the attack surface especially in environments where publish accounts are widely distributed or shared.
Mitigation Recommendations
To mitigate this vulnerability, organizations should immediately upgrade SiYuan Note to version 3.5.10 or later where the access control flaw has been fixed. Until patching is possible, restrict publish account creation and limit RoleReader privileges to trusted users only. Implement network segmentation and access controls to limit exposure of the publish service API endpoints to only authorized personnel. Monitor logs for unusual append operations or content modifications originating from low-privilege accounts. Employ application-layer firewalls or API gateways to enforce stricter role validation on the /api/block/appendHeadingChildren endpoint if possible. Conduct regular audits of notebook content integrity and maintain versioned backups to enable recovery from unauthorized modifications. Educate users about the risk of privilege escalation and enforce strong authentication mechanisms to reduce the likelihood of compromised accounts being used to exploit this vulnerability.
Affected Countries
United States, China, Germany, Japan, South Korea, United Kingdom, Canada, Australia, France, India
CVE-2026-30926: CWE-284: Improper Access Control in siyuan-note siyuan
Description
SiYuan is a personal knowledge management system. Prior to 3.5.10, a privilege escalation vulnerability exists in the publish service of SiYuan Note that allows low-privilege publish accounts (RoleReader) to modify notebook content via the /api/block/appendHeadingChildren API endpoint. The endpoint requires only the model.CheckAuth role, which accepts RoleReader sessions, but it does not enforce stricter checks, such as CheckAdminRole or CheckReadonly. This allows remote authenticated publish users with read-only privileges to append new blocks to existing documents, compromising the integrity of stored notes.
AI-Powered Analysis
Technical Analysis
SiYuan Note is a personal knowledge management system used for organizing and storing notes. In versions prior to 3.5.10, a critical access control vulnerability (CVE-2026-30926) exists in its publish service, specifically in the /api/block/appendHeadingChildren API endpoint. This endpoint is intended to allow users to append heading children blocks to notebooks. However, it only enforces a minimal authorization check (model.CheckAuth), which permits sessions with RoleReader privileges—intended as read-only access—to perform this action. The lack of stricter role enforcement such as CheckAdminRole or CheckReadonly means that users with read-only publish accounts can escalate their privileges to modify notebook content. This improper access control (CWE-284) and authorization bypass (CWE-862) flaw compromises the integrity of stored notes by allowing unauthorized content modification. The vulnerability is remotely exploitable by authenticated users without requiring user interaction beyond authentication. The CVSS v3.1 score of 7.1 reflects a high severity due to low attack complexity, network attack vector, and significant impact on integrity, though confidentiality and availability impacts are limited. No public exploits have been reported yet, but the vulnerability poses a serious risk to the integrity of knowledge assets managed by SiYuan Note users.
Potential Impact
The primary impact of this vulnerability is the compromise of data integrity within SiYuan Note notebooks. Unauthorized users with read-only publish accounts can append or modify content, potentially injecting misleading, malicious, or erroneous information. This can undermine trust in the knowledge management system, disrupt workflows, and cause misinformation to propagate within organizations. Since SiYuan Note is used for personal and collaborative knowledge management, the integrity breach could affect decision-making, documentation accuracy, and intellectual property. Although confidentiality and availability are not directly impacted, the ability to alter stored content without proper authorization represents a significant risk. Organizations relying on SiYuan Note for critical documentation or collaborative knowledge sharing are at risk of data tampering, which could have downstream effects on operational security and compliance. The vulnerability is exploitable remotely by authenticated users, increasing the attack surface especially in environments where publish accounts are widely distributed or shared.
Mitigation Recommendations
To mitigate this vulnerability, organizations should immediately upgrade SiYuan Note to version 3.5.10 or later where the access control flaw has been fixed. Until patching is possible, restrict publish account creation and limit RoleReader privileges to trusted users only. Implement network segmentation and access controls to limit exposure of the publish service API endpoints to only authorized personnel. Monitor logs for unusual append operations or content modifications originating from low-privilege accounts. Employ application-layer firewalls or API gateways to enforce stricter role validation on the /api/block/appendHeadingChildren endpoint if possible. Conduct regular audits of notebook content integrity and maintain versioned backups to enable recovery from unauthorized modifications. Educate users about the risk of privilege escalation and enforce strong authentication mechanisms to reduce the likelihood of compromised accounts being used to exploit this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-07T16:40:05.884Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69af3955ea502d3aa8c59c80
Added to database: 3/9/2026, 9:19:17 PM
Last enriched: 3/9/2026, 9:34:10 PM
Last updated: 3/13/2026, 10:01:08 PM
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.