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

CVE-2026-54158

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, the attribute-view (database) cell renderer genAVValueHTML interpolates cell content raw in four of its branches: text, url, phone, and mAsset. A cell value like </textarea><img src=x onerror="..."> or "><img src=x onerror="..."> breaks out of its surrounding tag and runs arbitrary JavaScript in the renderer when the victim opens the block-attribute panel. On Electron desktop the renderer runs with nodeIntegration:true, so the XSS chains to host RCE via require('child_process'). AV files live under the workspace and ride normal sync, so an attacker with write access to any synced workspace plants the payload once and it fires on every device that opens a panel containing that row.he kernel doesn't escape on the way in either, so the malicious cell persists byte-for-byte. There's no equivalent of the html.EscapeAttrVal call that protects block IAL attributes at kernel/model/blockial.go:261. 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

Stored XSS in SiYuan's attribute-view cell renderer (genAVValueHTML) allows injection via unsanitized cell content in text, url, phone, and mAsset cell types. Malicious payloads like `</textarea><img src=x onerror=...>` break out of surrounding HTML tags. On Electron desktop builds, nodeIntegration:true enables chaining to RCE via require('child_process'). The kernel also lacks input escaping, persisting the payload byte-for-byte across synced workspaces.

MitigationUpgrade to SiYuan 3.7.0 or later which implements proper escaping via html.EscapeAttrVal. Until patched, avoid opening block-attribute panels from untrusted or shared workspaces.

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 installed SiYuan version
    Open SiYuan and navigate to Help > About, or check the application binary metadata for the version number
    Affected if The version is prior to 3.7.0 (e.g., 3.6.x, 3.5.x, etc.)
  2. Identify Electron desktop build configuration
    Locate the Electron main process configuration file (usually named main.js, index.js, or packaged within the app resources) and inspect webPreferences for nodeIntegration:true setting
    Affected if nodeIntegration is set to true, which would allow the XSS to escalate to RCE via require('child_process')
  3. Determine if block-attribute panel feature is accessible
    In the SiYuan interface, attempt to open the block-attribute panel (typically via right-click > Block Attributes or a keyboard shortcut)
    Affected if Users have access to the block-attribute panel, which is the trigger point for the XSS execution
  4. Check workspace sync configuration
    Inspect the workspace sync settings in SiYuan (Settings > Sync) to determine if workspace sync is enabled
    Affected if Workspace sync is enabled, as the vulnerability allows malicious cells to persist byte-for-byte across synced workspaces

You are affected if you are running SiYuan version prior to 3.7.0 AND users can access the block-attribute panel, with higher severity if nodeIntegration is enabled in Electron builds.

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 which implements proper escaping via html.EscapeAttrVal. Until patched, avoid opening block-attribute panels from untrusted or shared workspaces.

Recommended fix High confidence

SiYuan version 3.7.0 or later

  1. 1. Identify the current SiYuan version installed by checking the application settings or about section
  2. 2. Download SiYuan version 3.7.0 or later from the official GitHub releases repository (github.com/siyuan-note/siyuan)
  3. 3. Backup the current workspace data before upgrading to ensure data preservation
  4. 4. Install version 3.7.0 or newer following standard installation procedures for your platform (Windows/macOS/Linux)
  5. 5. After upgrading, verify the block-attribute panel functions correctly with various cell content types
  6. 6. For Electron desktop users: confirm nodeIntegration settings in the application if running in a shared environment
Caveat Review release notes for 3.7.0 to check for any breaking changes in database/attribute-view functionality or sync behavior

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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