SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, SiYuan's Bazaar (community marketplace) renders the name and version fields of a package's plugin.json (and the equivalent theme.json / template.json / widget.json / icon.json) into the Settings → Marketplace UI without HTML escaping. The kernel-side helper sanitizePackageDisplayStrings in kernel/bazaar/package.go HTML-escapes only Author, DisplayName, and Description — Name and Version flow through to the renderer raw. The frontend at app/src/config/bazaar.ts substitutes them into HTML template strings via ${item.preferredName} / ${data.name} / v${data.version} and assigns the result to innerHTML. As a consequence, malicious HTML in either field is parsed and executed when a user opens the marketplace tab. This vulnerability is fixed in 3.7.0.
CVE-2026-45375
Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-13. NVD baseline CVSS 9.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fixed version is listed under Patch Availability — apply it.
- CVSS v3
- 9.0
- EG Score
- 9.0CRITICALmedium confidence
- EG Risk
- 57EG Risk 57/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation40% × 40%Automatability0% × 15% - EPSS PROB
- 0.4%
- EPSS %ILE
- 33rd
- KEV
- Not listed
Published
May 14, 2026
Last Modified
May 16, 2026
Advisory Details (1)
Auto-updated May 14, 2026SiYuan Bazaar marketplace renders unescaped package `name` and `version` metadata, allowing stored XSS and Electron code execution · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-27qc-m5gf-jv5rVendor Advisories for CVE-2026-45375(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/siyuan-note/siyuan/kernel | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/siyuan-note/siyuan/kernel | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 343 total refreshes for this CVE.
- 2026-10-10 20:00 UTCEPSS rescore
- 2026-10-09 20:07 UTCEPSS rescore
- 2026-10-08 17:12 UTCEPSS rescore
- 2026-10-07 23:48 UTCEPSS rescore
- 2026-10-06 15:18 UTCEPSS rescore
- 2026-10-05 17:43 UTCEPSS rescore
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 10:47 UTCOSV refresh
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:58 UTCEPSS rescore
- 2026-09-23 17:53 UTCEPSS rescore
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 17:40 UTCOSV refresh
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 21:16 UTCGHSA enrichment
- 2026-08-23 17:38 UTCEG score recompute
- 2026-08-23 17:38 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:47 UTCEG score recompute
- 2026-08-22 01:47 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 19:34 UTCEG score recompute
- 2026-08-20 19:34 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:00 UTCEG score recompute
- 2026-08-17 14:00 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:22 UTCEG score recompute
- 2026-08-17 10:22 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:18 UTCGHSA enrichment
- 2026-08-16 07:40 UTCGHSA enrichment
- 2026-08-16 03:55 UTCEG score recompute
- 2026-08-16 03:55 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:15 UTCGHSA enrichment
- 2026-08-14 20:37 UTCGHSA enrichment
- 2026-08-14 16:59 UTCGHSA enrichment
- 2026-08-14 13:18 UTCGHSA enrichment
- 2026-08-14 09:40 UTCGHSA enrichment
- 2026-08-14 06:02 UTCGHSA enrichment
- 2026-08-14 02:24 UTCEG score recompute
- 2026-08-14 02:24 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:35 UTCGHSA enrichment
- 2026-08-13 05:55 UTCGHSA enrichment
- 2026-08-13 01:52 UTCGHSA enrichment
- 2026-08-12 22:14 UTCGHSA enrichment
- 2026-08-12 18:36 UTCGHSA enrichment
- 2026-08-12 14:58 UTCEG score recompute
- 2026-08-12 14:58 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 22:56 UTCGHSA enrichment
- 2026-08-11 19:13 UTCGHSA enrichment
- 2026-08-11 15:24 UTCEG score recompute
- 2026-08-11 15:24 UTCGHSA enrichment
- 2026-08-11 08:07 UTCGHSA enrichment
- 2026-08-11 04:29 UTCGHSA enrichment
- 2026-08-11 00:51 UTCEG score recompute
- 2026-08-11 00:51 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 14:11 UTCGHSA enrichment
- 2026-08-10 10:32 UTCGHSA enrichment
- 2026-08-10 06:54 UTCGHSA enrichment
- 2026-08-10 03:16 UTCGHSA enrichment
- 2026-08-09 23:38 UTCGHSA enrichment
- 2026-08-09 20:00 UTCGHSA enrichment
- 2026-08-09 16:22 UTCEG score recompute
- 2026-08-09 16:22 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:44 UTCGHSA enrichment
- 2026-08-09 09:05 UTCGHSA enrichment
- 2026-08-09 05:27 UTCGHSA enrichment
- 2026-08-09 01:49 UTCGHSA enrichment
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/siyuan-note/siyuan/kernel
- CVE-2026-72811EG 10.0CRITICAL
- CVE-2026-69085EG 10.0CRITICAL
- CVE-2026-69084EG 10.0CRITICAL
- CVE-2026-69083EG 10.0CRITICAL
- CVE-2026-54158EG 9.9CRITICAL
- CVE-2026-54067EG 9.9CRITICAL
- CVE-2026-50551EG 9.9CRITICAL
- CVE-2026-32938NVD 6.5EG 9.9CRITICAL
- CVE-2026-33670NVD 7.5EG 9.8CRITICAL
- CVE-2026-33669NVD 7.5EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-45375?
When was CVE-2026-45375 disclosed?
Is CVE-2026-45375 actively exploited?
What is the CVSS score of CVE-2026-45375?
How do I remediate CVE-2026-45375?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45375
Is Your Infrastructure Affected by CVE-2026-45375?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.