# CVE-2026-45375: SiYuan Bazaar marketplace renders unescaped package `name` and `version` metadata, allowing stored XSS and Electron code execution

> Attackers can execute arbitrary code via stored XSS in the marketplace UI by injecting malicious HTML into package metadata fields.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 16 May 2026
- **Also known as:** GHSA-27qc-m5gf-jv5r, GO-2026-5001

## What is CVE-2026-45375?

CVE-2026-45375 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 14 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2026-45375?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | None |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20260421031503-96dfe0bea474 | None |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions to 0.0.0-20260421031503-96dfe0bea474 | None |

## How do I fix CVE-2026-45375?

Upgrade to a fixed version.

## Is CVE-2026-45375 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45375 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45375 and fix it if it is affected.

What it is: CVE-2026-45375 is a critical cross-site scripting vulnerability in siyuan-note siyuan, published on 14 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45375 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260421031503-96dfe0bea474; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions up to 0.0.0-20260421031503-96dfe0bea474; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45375/ (Markdown: https://insights.sbomify.com/CVE-2026-45375/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45375
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45375
- OSV: https://osv.dev/vulnerability/CVE-2026-45375

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45375/
Summaries are generated and may contain mistakes; the official description above is the record.