Skip to main content
VulnerabilityPublished Updated

CVE-2026-32751: siyuan · Cross-site Scripting

Affects siyuanSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 3.6.1 when convenient.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade siyuan and siyuan-note/siyuan to 3.6.1.

Affected software

ProductAffectedFixed in
siyuan-notesiyuanAffected
  • <3.6.1
Fixed in
  • 3.6.1
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • <3.6.1
Fixed in
  • 3.6.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-32751, organizations should immediately upgrade all SiYuan installations to version 3.6.1 or later, where the vulnerability is patched by proper HTML escaping in the mobile file tree component. Additionally, restrict notebook rename privileges to trusted users only, minimizing the number of accounts capable of injecting malicious content. Review and harden Electron application configurations by disabling nodeIntegration and enabling contextIsolation to reduce the impact of any future XSS vulnerabilities. Implement network segmentation and endpoint protection to detect and prevent exploitation attempts. Monitor WebSocket traffic and application logs for suspicious renamenotebook events or unexpected HTML content. Educate users about the risks of interacting with untrusted notebook names and encourage reporting of unusual behavior. Finally, consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect exploitation attempts in real time.

Description

SiYuan is a personal knowledge management system. In versions 3.6.0 and below, the mobile file tree (MobileFiles.ts) renders notebook names via innerHTML without HTML escaping when processing renamenotebook WebSocket events. The desktop version (Files.ts) properly uses escapeHtml() for the same operation. An authenticated user who can rename notebooks can inject arbitrary HTML/JavaScript that executes on any mobile client viewing the file tree. Since Electron is configured with nodeIntegration: true and contextIsolation: false, the injected JavaScript has full Node.js access, escalating stored XSS to full remote code execution. The mobile layout is also used in the Electron desktop app when the window is narrow, making this exploitable on desktop as well. This issue has been fixed in version 3.6.1.

References

Community reviews

Loading reviews…