dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-45375

CRITICAL · 9.0 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SiYuan's Bazaar marketplace feature has a stored XSS vulnerability where the Name and Version fields from plugin.json (and similar JSON files) are rendered in the Settings → Marketplace UI without HTML escaping. While the kernel helper sanitizePackageDisplayStrings escapes Author, DisplayName, and Description, the Name and Version fields flow through to the frontend raw, where they are inserted into innerHTML via template strings, allowing arbitrary JavaScript execution.

MitigationUpdate SiYuan to version 3.7.0 or later which includes proper HTML escaping for the Name and Version fields in the sanitizePackageDisplayStrings function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SiYuan application version
    Open SiYuan, go to Settings → About, or check the installation directory for version information. The version is typically displayed in the UI footer or in the application's config/data files.
    Affected if The installed version is earlier than 3.7.0 (versions 3.6.x and earlier are affected)
  2. Verify Bazaar marketplace feature is accessible
    Navigate to Settings → Marketplace in the SiYuan application. The vulnerability exists in this marketplace UI where plugin information is displayed.
    Affected if The Marketplace UI is accessible and displays plugin information from plugin.json files
  3. Identify installed plugins with plugin.json files
    Locate the plugins directory in the SiYuan data folder (typically named plugins or workspace/plugins). Examine each plugin.json file for the Name and Version fields.
    Affected if Any plugins are installed with plugin.json files containing Name and Version fields that could contain unsanitized input
  4. Inspect rendered marketplace display for escaping
    In the Marketplace UI, view plugin details. The vulnerability allows Name and Version fields to be inserted into innerHTML without escaping. If you can view page source or use browser dev tools, check if Name/Version values appear unescaped in HTML context.
    Affected if The Name and Version fields from plugin.json render as raw HTML in the marketplace UI without HTML entity encoding

A user is affected if they are running SiYuan version earlier than 3.7.0 and have access to the Bazaar marketplace feature where plugins with plugin.json files are displayed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SiYuan to version 3.7.0 or later which includes proper HTML escaping for the Name and Version fields in the sanitizePackageDisplayStrings function.

Recommended fix High confidence

SiYuan 3.7.0

  1. Ensure you have a backup of your SiYuan data before upgrading
  2. Download SiYuan version 3.7.0 or later from the official releases (github.com/siyuan-note/siyuan/releases)
  3. Stop the current SiYuan instance
  4. Install version 3.7.0 following standard installation procedures
  5. Restart SiYuan and verify the marketplace functionality works correctly
  6. Confirm the upgrade was successful by checking the SiYuan version in Settings → About

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45375 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data