CVE-2026-103762 — SiYuan before v3.8.5 Missing Authorization in Save-Path Resolver Endpoints

SiYuan before v3.8.5 contains a missing authorization vulnerability in the getRefCreateSavePath, getShorthandSavePath, and getDocCreateSavePath endpoints that allows read-only publish visitors to learn unpublished notebook box IDs. Attackers with read-only or anonymous publish access can POST any open notebook ID to receive the global save-box ID and save-path template, revealing a hidden notebook's existence and creation time.

Published Oct 2, 2026Updated Oct 2, 2026Sources: cvelistV5, VulnCheck

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

siyuan note

siyuan

CVSS base

5.3

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

siyuan note

Products (1)

siyuan

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.3	CVSS 3.1	MEDIUM	—	—	cvelistV5

Weakness & attack patterns

CWE-862

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1211Exploitation for Defensive Evasion
T1542.002Pre-OS Boot: Component Firmware
T1556Modify Authentication Process

References

2 on the record

github.com/siyuan-note/siyuan/security/advisories/GHSA-2mrf-mx66-vv6g
vendor-advisory
www.vulncheck.com/advisories/siyuan-before-3.8.5-missing-authorization-in-save-path-resolver-endpoints
third-party-advisory

Elsewhere on this site

siyuan noteevery CVE for this vendor
CWE-862other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.