CVE-2026-32940 — AI Deep Analysis Summary

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-79** (XSS). 🔍 **Flaw**: The `SanitizeSVG` filter uses an **incomplete blocklist** and fails to **escape user input**. Malicious SVG tags slip through the cracks.

Q: Who is affected? (Versions/Components)

📦 **Affected**: **SiYuan Note** (Personal Knowledge Management). 📅 **Versions**: **v3.6.0 and earlier**. If you are on an older version, you are at risk.

Q: Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exploit**: **No**. 📂 **PoCs**: Empty in data. 🌍 **Wild Exploitation**: None reported yet. It is a theoretical risk until a PoC is released.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: 1. Check your SiYuan version in Settings. 2. If **< v3.6.1**, you are vulnerable. 3. Scan for custom SVG imports in your notes that look suspicious.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. 🔧 **Patch**: Upgrade to **v3.6.1**. 🔗 **Links**: See GitHub Release v3.6.1 and GHSA-4mx9-3c2h-hwhg for details.

Q: What if no patch? (Workaround)

🛑 **No Patch Workaround**: 1. **Disable** SVG rendering if possible. 2. **Avoid** importing untrusted SVG files. 3. **Isolate** your SiYuan instance from the public internet if possible.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **High Priority**. 📉 **CVSS**: 8.1 (High). 💡 **Action**: Update immediately. Even without a public PoC, the flaw is critical for data privacy in a knowledge base.

Updated May 06, 2026 CVSS 9.3 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SiYuan v3.6.0- has a **Clickjacking/XSS** flaw in `SanitizeSVG`. <br>💥 **Consequences**: Attackers can inject malicious scripts via SVG inputs, leading to **Click-based Cross-Site Scripting**.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-79** (XSS). <br>🔍 **Flaw**: The `SanitizeSVG` filter uses an **incomplete blocklist** and fails to **escape user input**. Malicious SVG tags slip through the cracks.

Q3Who is affected? (Versions/Components)

📦 **Affected**: **SiYuan Note** (Personal Knowledge Management). <br>📅 **Versions**: **v3.6.0 and earlier**. If you are on an older version, you are at risk.

Q4What can hackers do? (Privileges/Data)

🕵️ **Hacker Actions**: Execute arbitrary JavaScript in your context. <br>🔓 **Privileges**: Steal cookies, session tokens, or perform actions on your behalf.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚠️ **Threshold**: **Medium**. <br>🖱️ **Requirement**: **User Interaction (UI:R)**. The victim must **click** something.…

Read full answer (login)

Q6Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exploit**: **No**. <br>📂 **PoCs**: Empty in data. <br>🌍 **Wild Exploitation**: None reported yet. It is a theoretical risk until a PoC is released.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Check your SiYuan version in Settings. <br>2. If **< v3.6.1**, you are vulnerable. <br>3. Scan for custom SVG imports in your notes that look suspicious.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. <br>🔧 **Patch**: Upgrade to **v3.6.1**. <br>🔗 **Links**: See GitHub Release v3.6.1 and GHSA-4mx9-3c2h-hwhg for details.

Q9What if no patch? (Workaround)

🛑 **No Patch Workaround**: <br>1. **Disable** SVG rendering if possible. <br>2. **Avoid** importing untrusted SVG files. <br>3. **Isolate** your SiYuan instance from the public internet if possible.

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **High Priority**. <br>📉 **CVSS**: 8.1 (High). <br>💡 **Action**: Update immediately. Even without a public PoC, the flaw is critical for data privacy in a knowledge base.

Continue exploring

Vulnerability detail Full AI analysis (login) siyuan-note CWE-79