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

CVE-2026-50551

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

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 contains a stored cross-site scripting (XSS) vulnerability in the Attribute View (database) asset cell renderer that escalates to remote code execution (RCE) in the Electron desktop client. 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 prior to 3.7.0 contains a stored cross-site scripting vulnerability in the Attribute View (database) asset cell renderer. When exploited in the Electron desktop client, this XSS can be chained to achieve remote code execution, giving attackers full system access.

MitigationUpgrade SiYuan to version 3.7.0 or later. Until then, restrict access to untrusted users and disable the Electron desktop client if possible.

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 if SiYuan is installed
    Look for SiYuan application in system (Windows: Program Files or AppData, macOS: Applications folder, Linux: standard application paths). Also check for running processes named 'siyuan' or 'SiYuan'.
    Affected if SiYuan application is present on the system
  2. Identify installed SiYuan version
    In the desktop client: Help > About. In the kernel: check /workspace/siyuan/kernel/version.go or run 'siyuan --version' if CLI available. Compare the version number to 3.7.0.
    Affected if Version is lower than 3.7.0 (e.g., 3.6.x, 3.5.x, etc.)
  3. Determine if using Electron desktop client
    Check if running the desktop Electron app versus browser/web client. The Electron client typically has 'SiYuan' in the window title and runs as a standalone desktop process. The XSS-to-RCE chain only applies to the Electron client.
    Affected if Running the Electron desktop client version lower than 3.7.0
  4. Check if Attribute View/database is accessible
    Within SiYuan, create or open a notebook and navigate to any document. Create or view an Attribute View (database) panel. The vulnerability exists in the asset cell renderer of this feature.
    Affected if Attribute View (database) feature is in use with a version below 3.7.0

User is affected if SiYuan Electron desktop client version is below 3.7.0 and the Attribute View (database) feature is accessible to untrusted users.

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

Upgrade SiYuan to version 3.7.0 or later. Until then, restrict access to untrusted users and disable the Electron desktop client if possible.

Recommended fix High confidence

3.7.0

  1. 1. Check the current installed version of SiYuan (Help > About in the application menu)
  2. 2. Back up the SiYuan data directory (by default at ~/SiYuan/ or C:\Users\<user>\SiYuan\) to ensure data safety before upgrading
  3. 3. Download SiYuan version 3.7.0 or later from the official GitHub releases page (https://github.com/siyuan-note/siyuan/releases)
  4. 4. For desktop users: Close the running SiYuan application completely
  5. 5. Install the downloaded version 3.7.0 (or newer) by running the installer for your platform (Windows/macOS/Linux)
  6. 6. After installation, verify the new version by checking Help > About to confirm version 3.7.0 or later is running
  7. 7. If using the Electron desktop client, test that the Attribute View (database) functionality works correctly with asset cells

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50551 — 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-50551 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