SiYuan through 3.8.4 Access Control Bypass via Dynamic Icon Endpoint
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.2%
exploitation probability
0.2%top 86% of all CVEs
observed exploitation
nono source reports it
SiYuan versions through 3.8.4 fail to enforce publish access control in the getDynamicIcon endpoint, allowing read-only token holders to access document metadata. Attackers can call the endpoint with type=8 and crafted content to read block titles, names, aliases, and hierarchical paths of restricted documents via template injection.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
siyuan-note · siyuanReferences
https://github.com/siyuan-note/siyuanhttps://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/api/icon.go#L546-L549https://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/api/router.go#L51https://github.com/siyuan-note/siyuan/blob/v3.8.4/kernel/model/template.go#L485-L526https://github.com/siyuan-note/siyuan/security/advisories/GHSA-whcx-xxqh-c838https://www.vulncheck.com/advisories/siyuan-through-3.8.4-access-control-bypass-via-dynamic-icon-endpoint