Security readout for executives and security teams
Plain-English summary
SiYuan through version 3.7.2 lets certain remote users submit unrestricted database instructions through a search API. This can expose or alter content across opened cleartext notebooks. Anonymous access is possible when publish authentication is disabled; a publish reader token may also suffice. Version 3.7.3 fixes the flaw.
Executive priority
Treat as an immediate remediation priority for any network-accessible SiYuan deployment. Accelerate upgrades where publishing is anonymous or reader tokens are broadly available. Investigate possible data exposure or tampering if vulnerable systems were reachable by untrusted parties.
Technical view
The searchEmbedBlock API passes client-supplied SQL directly to SiYuan’s primary read-write database connection. It lacks single-statement, read-only, and administrator restrictions, while the database driver accepts stacked statements. Authentication checks still permit publish RoleReader access and potentially anonymous access. Per-box encrypted notebooks are excluded.
Likely exposure
Deployments running SiYuan 3.7.2 or earlier are affected. Exposure is greatest when the API is network-accessible, publish authentication is disabled, or reader tokens are distributed. Opened cleartext notebooks may be affected; the supplied evidence excludes encrypted per-box notebooks.
Exploitation context
The flaw is remotely reachable with low complexity and requires no user interaction. The supplied CVSS score is 10.0. However, the CVE is not listed as KEV in the bundle, and the cited evidence does not establish active exploitation in the wild.
Researcher notes
CWE-89 applies. The critical issue is not merely SQL construction: attacker-controlled statements reach a read-write handle capable of stacked execution. Scope includes content across opened cleartext notebooks. Evidence supplied does not quantify affected installations, confirm exploitation, or describe indicators beyond the vulnerable endpoint.
Mitigation direction
- Upgrade SiYuan to version 3.7.3 or later.
- Until upgraded, require publish authentication and restrict network access to trusted users.
- Review the vendor advisory for any additional deployment-specific guidance.
- Rotate publish reader tokens if unauthorized access is suspected.
Validation and detection
- Inventory all SiYuan deployments and identify versions 3.7.2 or earlier.
- Confirm every deployment now runs version 3.7.3 or later.
- Verify publish authentication is enabled and anonymous API access is unavailable.
- Review available logs for unexpected requests to /api/search/searchEmbedBlock.
- Assess opened cleartext notebooks for unauthorized content changes or disclosure.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. 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-69084 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
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
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:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N3.95.8VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.9CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
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-vh22-h7hf-www7)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SiYuan before v3.7.3 SQL Injection via searchEmbedBlockCVE 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.