CVE-2026-73053: SiYuan before v3.7.4 Cross-Site Scripting via unicode2Emoji
SiYuan versions before v3.7.4 contain a cross-site scripting vulnerability in the unicode2Emoji function that fails to sanitize codepoint branch output. Attackers can craft document icons with hex-encoded markup that executes in the renderer with Node integration enabled, achieving arbitrary code execution on the host system.
Security readout for executives and security teams
Plain-English summary
A maliciously crafted SiYuan document icon can cross a trust boundary from displayed content into executable code. On vulnerable systems where the renderer has Node integration enabled, successful exploitation can compromise the host, including its data and availability.
Executive priority
Treat this as an urgent remediation item. Prioritize internet-accessible or shared SiYuan environments, especially those accepting untrusted content. The potential impact is full host compromise, although active exploitation is not established by the supplied evidence.
Technical view
SiYuan before v3.7.4 does not sanitize output from the codepoint branch of unicode2Emoji. Hex-encoded markup in a document icon can trigger cross-site scripting in the renderer. With Node integration enabled, that script can execute arbitrary code on the host. The CVSS 4.0 score is 9.4.
Likely exposure
Exposure is most likely where SiYuan versions earlier than v3.7.4 process attacker-influenced document icons and Node integration is enabled. The supplied evidence does not establish how common that configuration is or whether all deployment modes are equally exposed.
Exploitation context
The CVSS vector indicates network reachability, low complexity, low privileges, and passive user interaction. The supplied sources describe a path to host code execution, but provide no evidence of observed exploitation. This CVE is not identified as KEV in the bundle.
Researcher notes
The vulnerable data flow is the unsanitized codepoint output from unicode2Emoji into a privileged renderer. CWE-79 understates the practical consequence because Node integration converts renderer script execution into host code execution. Safely validate version, configuration, and content provenance without rendering suspicious icons on production systems.
Mitigation direction
Upgrade SiYuan to v3.7.4 or a later vendor-supported release.
Review the vendor advisory for any additional configuration-specific guidance.
Restrict untrusted users or content from supplying document icons until upgraded.
Reduce exposure of vulnerable instances where operationally feasible.
Validation and detection
Inventory SiYuan installations and identify versions earlier than v3.7.4.
Determine whether affected renderers have Node integration enabled.
Review document icons from untrusted sources for suspicious hex-encoded markup.
Confirm upgraded installations report v3.7.4 or later.
Monitor affected hosts for unexpected processes or changes associated with SiYuan use.
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.