CVE-2026-73044: SiYuan before v3.7.4 Stored Cross-Site Scripting via Column Width
SiYuan versions before v3.7.4 fail to validate or escape table column width values, allowing stored cross-site scripting injection into style attributes. Attackers can inject malicious payloads through the setAttrViewColWidth API that break out of style attributes and inject event handlers on every table cell, executing arbitrary code in the Electron renderer with Node integration enabled.
Security readout for executives and security teams
Plain-English summary
A logged-in attacker can hide malicious content in a SiYuan table’s column-width setting. When someone views the affected table, code may run inside SiYuan’s desktop application with access to powerful Node capabilities, potentially compromising data and the host environment.
Executive priority
Treat this as an urgent desktop application update. Prioritize collaborative or externally reachable SiYuan deployments because a low-privileged account can plant persistent content that executes when another user views a table, with potential impact beyond the application’s data.
Technical view
SiYuan before 3.7.4 does not safely validate or escape table column-width values accepted by setAttrViewColWidth. Stored input can escape a style attribute and add event handlers to table cells. Rendering the table triggers code in an Electron renderer with Node integration enabled. The supplied CVSS 4.0 score is 9.4.
Likely exposure
Exposure is highest for SiYuan installations below 3.7.4 where lower-privileged or untrusted authenticated users can modify table attributes and another user subsequently views the table. Internet reachability increases opportunity, but the supplied evidence does not establish which deployment modes expose the affected API.
Exploitation context
Exploitation requires low privileges and a victim interaction, according to the supplied CVSS vector. The malicious value persists and may execute whenever affected table cells render. The bundle marks this CVE as absent from KEV, and the supplied evidence does not establish active exploitation in the wild.
Researcher notes
The core issue is CWE-79 at a style-attribute serialization boundary, amplified by Electron Node integration. The supplied affected-version metadata is compact and potentially ambiguous, but the title and description consistently identify versions before 3.7.4. No supplied source proves public exploitation or inclusion in KEV.
Mitigation direction
Upgrade SiYuan to version 3.7.4 or later.
Confirm the installed build and update status across every SiYuan deployment.
Until upgraded, restrict document editing and API access to trusted users.
Review the vendor advisory for any additional deployment-specific guidance.
Validation and detection
Inventory SiYuan versions and flag every installation earlier than 3.7.4.
Verify updated clients report version 3.7.4 or later.
Review stored table column-width attributes for unexpected markup or event-handler content.
Investigate logs for suspicious use of the setAttrViewColWidth API.
Confirm affected content no longer produces executable attributes after remediation.
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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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: pocAutomatable: 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.