Security readout for executives and security teams
Plain-English summary
SiYuan installations before version 3.7.4 can reveal a secret used to validate login cookies when operating in publish mode. An unauthenticated attacker could use that secret to impersonate users or obtain administrative access. Internet-accessible publish-mode deployments require urgent review.
Executive priority
Treat this as an immediate remediation item for externally reachable publish-mode deployments. Secret disclosure can bypass normal authentication and expose privileged accounts. Upgrade promptly, assess possible prior access, and follow vendor instructions for invalidating trust derived from the disclosed key.
Technical view
The unauthenticated /api/system/getConf endpoint exposes the CookieKey session-signing secret in publish mode. Possession of this key enables forged session cookies without valid credentials. The supplied record assigns CVSS 4.0 score 9.2 and identifies CWE-522. The stated affected range is SiYuan before 3.7.4.
Likely exposure
Exposure requires a pre-3.7.4 SiYuan deployment operating in publish mode with the affected endpoint reachable by an unauthenticated party. Publicly accessible instances face the greatest risk. The bundle does not establish how commonly publish mode or the vulnerable versions are deployed.
Exploitation context
The vulnerability is remotely reachable, requires no privileges or user interaction, and has low attack complexity. The supplied bundle states that forged cookies can enable impersonation or administrative access. It is not listed as KEV, and the provided sources do not establish active exploitation.
Researcher notes
The core issue is disclosure of a reusable authentication secret, not password theft. Validation should avoid retaining or distributing exposed CookieKey values. The supplied evidence supports the affected mode, endpoint, impact, and fixed-version boundary, but provides no confirmed exploitation telemetry or deployment prevalence.
Mitigation direction
- Upgrade affected SiYuan installations to version 3.7.4 or later.
- Prioritize internet-accessible systems operating in publish mode.
- Restrict unauthenticated access until upgrading, following vendor guidance.
- Check vendor guidance for CookieKey rotation and session invalidation after possible exposure.
Validation and detection
- Inventory SiYuan versions and identify installations older than 3.7.4.
- Determine which installations operate in publish mode or expose it externally.
- Confirm unauthenticated configuration responses no longer disclose CookieKey after remediation.
- Review access logs for unexpected requests to /api/system/getConf.
- Verify existing sessions and signing keys are handled according to vendor guidance.
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-522: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCVE-2026-72794 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-34fj-mwm6-fjfg)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: siyuan before v3.7.4 Session Cookie Key Disclosure via getConfCVE 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.
Insufficiently Protected Credentials
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.