9.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-29183

CVE-2026-29183: SiYuan: Unauthenticated reflected SVG XSS in `/api/icon/getDynamicIcon` (`type=8`) enables arbitrary JavaScript execution

SiYuan is a personal knowledge management system. Prior to version 3.5.9, an unauthenticated reflected XSS vulnerability exists in the dynamic icon API endpoint "GET /api/icon/getDynamicIcon" when type=8, attacker-controlled content is embedded into SVG output without escaping. Because the endpoint is unauthenticated and returns image/svg+xml, a crafted URL can inject executable SVG/HTML event handlers (for example onerror) and run JavaScript in the SiYuan web origin. This can be chained to perform authenticated API actions and exfiltrate sensitive data when a logged-in user opens the malicious link. This issue has been patched in version 3.5.9.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-29183

CVE-2026-29183:

9.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/siyuan-note/siyuan/kernel	go	< 0.0.0-20260304034809-d68bd5a79391	0.0.0-20260304034809-d68bd5a79391

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a reflected Cross-Site Scripting (XSS) issue in the /api/icon/getDynamicIcon endpoint. The root cause is two-fold:

User-provided input from the content query parameter is directly embedded into an SVG template without proper XML/HTML escaping. This happens within the generateTypeEightSVG function, which is called by getDynamicIcon.
The resulting SVG string was then passed to a weak sanitizer, util.RemoveScriptsInSVG. As the function name implies, it only removed <script> tags, leaving other vectors for script execution like onerror attributes intact.

The patch addresses this by replacing the inadequate util.RemoveScriptsInSVG function with a new, more thorough util.SanitizeSVG function. The new function removes a wider range of dangerous tags (like iframe, object), event handler attributes (like onerror), and unsafe attribute values (like javascript: in href).

The analysis of the commit d68bd5a79391742b3cb2e14d892bdd9997064927 confirms this. The changes show RemoveScriptsInSVG being replaced by SanitizeSVG in two places: kernel/api/icon.go within the getDynamicIcon function (the primary vulnerable endpoint) and kernel/server/serve.go within the serveSVG function.

Therefore, the key functions that would appear in a runtime profile during exploitation are getDynamicIcon, which is the entry point for the attack, and RemoveScriptsInSVG, which is the function that fails to prevent it. The serveSVG function is also included as it contained the same vulnerable pattern.

Vulnerable functions

getDynamicIcon

kernel/api/icon.go

This function is the API endpoint that receives the malicious user input (`content`). It was responsible for calling the weak `RemoveScriptsInSVG` sanitizer before the patch, allowing unescaped SVG content to be reflected to the user, leading to XSS.

RemoveScriptsInSVG

kernel/util/misc.go

This is the vulnerable sanitization function. It only removed `<script>` tags, failing to remove other malicious SVG elements or attributes like `onerror`, which is the root cause of the XSS vulnerability. It was replaced by the more robust `SanitizeSVG` function.

serveSVG

kernel/server/serve.go

This function also used the vulnerable `RemoveScriptsInSVG` function to process SVG data. While the primary exploit path was through `getDynamicIcon`, this function was also vulnerable to XSS if it could be made to serve a malicious, user-provided SVG file.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.