CVE-2026-82654: SiYuan before v3.8.1 Stored XSS via block name
SiYuan before v3.8.1 fails to properly escape block name, alias, and memo fields in hint, backlink, and breadcrumb rendering functions. Attackers can set a block's name to contain HTML/script tags that execute when another user views documents referencing or displaying that block.
Security readout for executives and security teams
Plain-English summary
SiYuan versions before 3.8.1 can store unsafe content in block names, aliases, or memos. When another user encounters the affected block through document hints, backlinks, or breadcrumbs, attacker-controlled script may run in that user’s browser, potentially compromising information and actions available through their session.
Executive priority
Treat internet-accessible or multi-user affected deployments as an immediate remediation priority. Upgrade promptly and temporarily reduce untrusted editing access. Although active exploitation is not documented, stored script execution across user sessions creates substantial confidentiality and integrity risk.
Technical view
This is stored cross-site scripting caused by insufficient output escaping in hint, backlink, and breadcrumb rendering. A low-privileged attacker can place HTML or script content in block metadata; exploitation then requires another user to view an affected rendering context. The published CVSS 4.0 score is 9.3, with high confidentiality and integrity impact.
Likely exposure
Exposure is most likely in multi-user SiYuan deployments running versions earlier than 3.8.1 where untrusted or lower-privileged users can edit block names, aliases, or memos. Risk increases when other users routinely view documents containing references, backlinks, hints, or breadcrumbs for attacker-controlled blocks.
Exploitation context
The sources describe a network-accessible, low-complexity attack requiring low privileges and passive victim interaction. The malicious content persists and executes when rendered to another user. This CVE is not identified as KEV, and the supplied sources provide no evidence of active exploitation in the wild.
Researcher notes
CWE-79 applies. Relevant sinks are the hint, backlink, and breadcrumb rendering functions; relevant stored inputs are block name, alias, and memo fields. The supplied evidence does not identify specific commits, observed attacks, affected deployment modes, or indicators of compromise, so those details should not be inferred.
Mitigation direction
Upgrade affected SiYuan installations to version 3.8.1 or later, following vendor guidance.
Restrict untrusted users from editing block names, aliases, and memos until upgraded.
Limit access to affected collaborative instances where immediate upgrading is unavailable.
Review the vendor advisory for any additional remediation or release-specific instructions.
Validation and detection
Inventory every SiYuan deployment and confirm its installed version.
Verify upgraded systems report version 3.8.1 or later.
Review permissions for users who can edit block metadata.
Inspect block names, aliases, and memos for unexpected HTML or script-like content.
Safely regression-test that harmless markup is encoded in hints, backlinks, and breadcrumbs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.