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

CVE-2026-54067

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, CSS snippet body containing </style> breaks out of its surrounding <style> tag when renderSnippet() interpolates it via insertAdjacentHTML. A payload like runs arbitrary JavaScript in the renderer. On Electron desktop builds the renderer runs with nodeIntegration:true, so require('child_process') is reachable from the injected handler and the XSS chains to host RCE. Snippets sync via the workspace repository, so an attacker with write access to any synced workspace plants the payload once and it fires on every device that pulls. The bug also bypasses the user's enabledCSS / enabledJS separation. A user who turned enabledJS off was making a deliberate call not to run untrusted JavaScript; the CSS path runs it anyway. 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

A stored XSS vulnerability in SiYuan's CSS snippet rendering allows attackers to break out of the <style> tag context via </style> injection, enabling arbitrary JavaScript execution. In Electron desktop builds where nodeIntegration:true is enabled, this XSS chains to host RCE via require('child_process'). The payload persists via workspace repository sync, affecting all devices pulling the malicious snippet, and bypasses user-enabledJS protections.

MitigationUpgrade to SiYuan 3.7.0 or later to obtain the fixed renderSnippet() implementation and review Electron security settings to disable nodeIntegration if not already addressed in the update.

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 your SiYuan version
    Open SiYuan and go to Help > About, or check the application file properties to find the installed version number
    Affected if The version is below 3.7.0 (any version 3.6.x or earlier)
  2. Inspect CSS snippets for malicious payloads
    Access the workspace data directory and search all CSS snippet files for the string '</style>' using a text search or grep tool
    Affected if Any CSS snippet file contains the sequence '</style>' which could indicate an attempted breakout payload
  3. Verify if using Electron desktop build
    Confirm you are using the Electron-based desktop application rather than the browser-based or mobile versions of SiYuan
    Affected if You are running the desktop Electron build of SiYuan (the vulnerability chains to RCE only in Electron environments)
  4. Check Electron nodeIntegration setting
    If using the desktop build, examine the Electron configuration or main process files for the nodeIntegration setting value
    Affected if nodeIntegration is set to true in the Electron configuration (this enables the RCE chain via require('child_process')')

You are affected if running SiYuan below version 3.7.0 with a CSS snippet containing '</style>' present in your workspace, and particularly if using the Electron desktop build with nodeIntegration enabled.

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 to SiYuan 3.7.0 or later to obtain the fixed renderSnippet() implementation and review Electron security settings to disable nodeIntegration if not already addressed in the update.

Recommended fix High confidence

3.7.0

  1. Upgrade SiYuan to version 3.7.0 or later

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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