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

CVE-2026-59833

HIGH · 8.6 CVSS v4.0 Published 2026-07-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges Patch available 6 weeks old

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.1, SiYuan renders note and package content to HTML through the Lute engine with sanitization enabled, but Lute's dangerous javascript scheme block does not check form action or SVG xlink:href attributes, allowing stored cross-site scripting in document export-preview and Bazaar package README render paths that can execute OS commands in the Electron desktop renderer. This issue is fixed in versions 3.7.1.

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.1 contains a stored XSS vulnerability in the Lute HTML rendering engine. The engine's javascript scheme block fails to sanitize form action and SVG xlink:href attributes, allowing malicious scripts to be embedded in document export-preview and Bazaar package README content. When rendered in the Electron desktop application, these scripts can execute OS commands.

MitigationUpgrade SiYuan to version 3.7.1 or later to obtain the fixed Lute engine with proper attribute sanitization.

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
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm SiYuan installation
    Locate the SiYuan application binary or installation directory. On Windows, check Program Files or AppData folders for 'SiYuan' folder. On macOS, check /Applications or ~/Applications. On Linux, check /opt or ~/.local/share.
    Affected if SiYuan is installed and running on the system.
  2. Identify installed SiYuan version
    Open SiYuan and navigate to Settings > About, or right-click the application icon and select 'About SiYuan'. The version number is displayed there.
    Affected if The installed version is prior to 3.7.1 (e.g., 3.7.0, 3.6.x, or earlier).
  3. Check for document export-preview usage
    In SiYuan, look for documents that have been exported using the export feature, particularly HTML export. Check the exported files in the export output directory for any custom form elements or SVG content.
    Affected if Exported HTML documents contain form elements with action attributes or SVG elements with xlink:href attributes that reference javascript: URIs.
  4. Inspect Bazaar package README content
    Open SiYuan's Bazaar marketplace panel. Navigate to installed plugins or themes. Inspect any README.md files associated with these packages for suspicious form or SVG markup.
    Affected if Bazaar package README files contain form tags with action="javascript:..." or SVG elements using xlink:href with javascript: scheme.
  5. Verify Lute rendering engine is active
    In SiYuan settings, check the markdown/HTML rendering configuration. The Lute engine is the default renderer for document preview and export. No configuration change is needed as it is enabled by default.
    Affected if Lute engine handles document rendering (default behavior in versions prior to 3.7.1).

You are affected if SiYuan is installed with a version lower than 3.7.1 and you have used document export-preview or installed Bazaar packages with custom README content containing form or SVG elements.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade SiYuan to version 3.7.1 or later to obtain the fixed Lute engine with proper attribute sanitization.

Recommended fix High confidence

3.7.1

  1. 1. Back up your SiYuan data and configuration before upgrading
  2. 2. Download SiYuan version 3.7.1 or later from the official GitHub releases page or the official website
  3. 3. Stop the running SiYuan instance or close the Electron desktop application
  4. 4. Install the upgraded version (3.7.1) following the standard installation procedure for your platform
  5. 5. Restart SiYuan and verify the application functions normally

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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