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

CVE-2026-44670

CRITICAL · 9.4 CVSS v4.0 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 kernel stores Attribute View (AV / database) names without any HTML escape, then a render template uses raw strings.ReplaceAll(tpl, "${avName}", nodeAvName) to embed the name in HTML before pushing to all clients via WebSocket. Three independent client paths (render.ts:120 → outerHTML, Title.ts:401 → innerHTML, transaction.ts:559 → innerHTML) consume the value without escaping. Because the main BrowserWindow runs nodeIntegration:true, contextIsolation:false, webSecurity:false (app/electron/main.js:407-411), HTML injection in the renderer becomes Node.js code execution. 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 (AV) names allows injection of malicious HTML/JavaScript. The kernel stores AV names without HTML escaping, and three render paths (render.ts, Title.ts, transaction.ts) insert these names directly into DOM via innerHTML/outerHTML. Combined with insecure Electron settings (nodeIntegration:true, contextIsolation:false, webSecurity:false), arbitrary JavaScript executes with Node.js privileges, enabling full RCE.

MitigationUpgrade to SiYuan v3.7.0 or later, which implements HTML escaping on AV names and hardens Electron security settings. If unable to upgrade immediately, restrict access to trusted users only.

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
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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. Identify SiYuan installation and version
    Locate the SiYuan application and check its version number via Help > About in the app, or check the installed package version
    Affected if Version is below 3.7.0
  2. Verify Electron security configuration
    Examine the Electron configuration files (typically in the app resources or config) for settings: nodeIntegration, contextIsolation, webSecurity
    Affected if nodeIntegration is true, contextIsolation is false, or webSecurity is false
  3. Confirm Attribute View usage
    Check if any workspaces contain Attribute Views by examining the data directory for AV-structured blocks or database entries
    Affected if Attribute Views exist in the workspace
  4. Inspect AV names for injection patterns
    Review stored AV names in the workspace data for raw HTML or script tags that may have been inserted without escaping
    Affected if AV names contain unescaped HTML or script tags

User is affected if running SiYuan version below 3.7.0 with insecure Electron security settings and using the Attribute View feature with potentially malicious AV names.

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 v3.7.0 or later, which implements HTML escaping on AV names and hardens Electron security settings. If unable to upgrade immediately, restrict access to trusted users only.

Recommended fix High confidence

3.7.0

  1. 1. Ensure you have a complete backup of your SiYuan data before upgrading.
  2. 2. Download SiYuan version 3.7.0 or later from the official GitHub releases (github.com).
  3. 3. Install the new version, preserving your existing data directory when prompted.
  4. 4. After upgrade, verify that Attribute View names are now properly escaped in the UI.
  5. 5. Confirm the Electron configuration has been hardened (nodeIntegration should be false, contextIsolation should be true).
Caveat Review release notes for any breaking changes between your current version and 3.7.0, particularly regarding plugin compatibility

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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