Security readout for executives and security teams
Plain-English summary
A development-only SiYuan build briefly exposed database search results without proper authorization. An anonymous visitor could potentially see rows intentionally hidden by publishing filters. The flaw was not present in released v3.7.3 or the master branch, and it was patched in v3.7.4. Business risk is serious only where the affected development code was deployed.
Executive priority
Immediately identify any development-branch SiYuan deployments. Replace affected builds and investigate possible disclosure where publishing was internet-accessible. Stable v3.7.3 installations do not require emergency action for this CVE, although normal upgrade practices remain appropriate.
Technical view
The endpoint /api/av/getAttributeViewSearchTarget used CheckAuth but omitted read-only, publishing-access, and encrypted-notebook authorization controls. An unauthenticated reader with a database identifier and keyword could retrieve matching content excluded by FilterAttributeViewByPublishAccess. This is CWE-862 with CVSS 4.0 score 9.2. The endpoint existed only in a development branch and was corrected in v3.7.4.
Likely exposure
Exposure is narrow despite the critical technical severity. No released stable version is affected. Risk applies to organizations that built or deployed the development branch containing commit 9b8e8956f before the v3.7.4 correction, particularly when SiYuan publishing features were internet-accessible and contained restricted database rows.
Exploitation context
The vulnerability is remotely reachable, requires no privileges or user interaction, and could disclose sensitive database content. The supplied sources provide no evidence of active exploitation, and the CVE is not identified as CISA KEV. A database identifier from published content is a prerequisite, but this does not constitute an authorization boundary.
Researcher notes
The key distinction is build provenance, not a broad version range: the vulnerable endpoint was introduced on a development branch, was absent from stable v3.7.3 and master, and was patched in v3.7.4. The supplied metadata’s affected-version representation is ambiguous, so exposure decisions should rely on endpoint and commit presence. No integrity or availability impact is described.
Mitigation direction
- Replace affected development builds with SiYuan v3.7.4 or a later vendor-supported release.
- Avoid exposing development-branch builds to untrusted networks.
- If replacement is delayed, follow the vendor advisory to restrict access to the affected endpoint.
- Review published databases for sensitive rows that relied on publishing filters.
Validation and detection
- Confirm deployed SiYuan versions and record whether any were built from development commits.
- Verify the affected endpoint is absent or contains the v3.7.4 authorization correction.
- Review access logs for unexpected anonymous requests to the affected endpoint.
- Assess whether exposed published pages revealed identifiers linked to restricted database content.
- Confirm restricted rows remain inaccessible to anonymous readers after remediation.
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-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-73608 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.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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-9cqf-hhrq-7v45)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: SiYuan before v3.7.4 Authorization Bypass via getAttributeViewSearchTargetCVE 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.