Security readout for executives and security teams
Plain-English summary
A low-privileged attacker can place malicious content in a SiYuan database field name. When another user opens that database’s sort menu, the content can run as JavaScript. In affected desktop clients with Node integration, this may extend beyond application data compromise to execution of code on the user’s computer.
Executive priority
Treat this as an urgent upgrade because interaction with shared malicious content could compromise sensitive data and, on Node-enabled desktops, the endpoint itself. Prioritize exposed collaborative environments and privileged users. There is no supplied evidence of active exploitation, but the impact and low attack complexity justify prompt action.
Technical view
SiYuan versions before 3.7.4 fail to HTML-escape attribute-view field names before inserting them into sort-menu option elements through innerHTML. This creates stored cross-site scripting requiring field-renaming access and a victim to open the sort menu. The supplied CVSS 4.0 score is 9.4; Node-enabled desktop clients can expose the host to code execution.
Likely exposure
Deployments running SiYuan earlier than 3.7.4 are potentially affected. Risk is greatest for desktop clients with Node integration, especially where lower-trust users can rename fields in databases used by others. The supplied evidence does not establish exposure for any specific organization.
Exploitation context
Exploitation requires a low-privileged attacker to rename a database field and another user to open the affected sort menu. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Public technical advisories may increase future attacker interest.
Researcher notes
The vulnerable path combines persistent, unescaped field names with an innerHTML option-rendering sink. Privileges and user interaction are required, but persistence makes victim targeting practical. Host code execution is specifically tied to Node integration in the desktop client. The bundle does not provide observed exploitation, forensic indicators, or details about alternative mitigations.
Mitigation direction
- Upgrade every affected SiYuan installation to version 3.7.4 or later, following the vendor advisory.
- Prioritize desktop clients with Node integration and databases shared with lower-trust users.
- Restrict untrusted users from renaming database fields until affected installations are upgraded.
- Review the vendor advisory for any additional supported mitigations or release guidance.
Validation and detection
- Inventory SiYuan installations and record their exact versions, deployment types, and Node integration status.
- Confirm no deployed SiYuan version is earlier than 3.7.4.
- Review available history or audit records for unexpected database field-name changes.
- Verify updated clients safely display field names when users open the sort menu.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73052 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H2.36VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-g3jx-227v-x2x4)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SiYuan before v3.7.4 Stored XSS via Attribute-View Field NamesCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation
Improper Neutralization of Input During Web Page Generation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.