Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain on-path network position (LAN/Wi-Fi/MITM)
-
DeliveryObserve victim Basic Auth over plaintext HTTP
-
ExploitCapture publish-visitor-session-id cookie
-
ExecutionReplay cookie to publish endpoints
-
ImpactAccess authenticated publish content without password
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V12 - Secure Communication Transport encryption
|
| Exploitation Conditions | Requires ALL of: (1) SiYuan's publish service must be enabled and protected by Basic Auth; (2) the service must be served over plaintext HTTP rather than HTTPS/TLS, since the flaw is that session cookies lack Secure and SameSite attributes and travel in cleartext; (3) the attacker must hold an on-path/man-in-the-middle network position (AT:P) to observe the publish-visitor-session-id cookie during a legitimate Basic Auth exchange. LIMITING FACTORS: deploying the publish service behind TLS/HTTPS eliminates the cleartext exposure and effectively mitigates the attack; the attacker cannot exploit this remotely without network vantage between victim and server; the publish feature must be actively in use. No password knowledge or prior authentication by the attacker is needed once the cookie is captured (PR:N). |
| Impact | This is a genuine but conditionally-exploitable authentication bypass rather than a high-CVSS-low-real-risk item. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:H) scores 8.2, but the AT:P (attack requirement: present) metric is the crux - successful attack requires an on-path/man-in-the-middle position to observe the plaintext cookie, which materially limits opportunistic exploitation. There is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis, so all three exploitation-probability signals point to no confirmed or widespread exploitation; the risk is targeted and network-position-dependent, not internet-wide. Confidentiality impact is real (VC:H - replay grants access to authenticated publish endpoints) while integrity/availability are unaffected (VI:N/VA:N). Note a signal tension: the vendor scores AC:L, but the requirement for an on-path position is better captured as elevated difficulty - my independent CVSS 3.1 assessment uses AC:H for that reason, lowering my computed base to ~5.9 versus the vendor's 8.2. The root cause (CWE-319 cleartext transmission - cookies without Secure/SameSite over HTTP) is fully corroborated by the patch commits, which add a CredentialVersion binding and session revocation on password change. |
| Exploit ScenarioDerived | A victim runs SiYuan's publish service over plaintext HTTP on a shared or untrusted network. An attacker positioned on the path (e.g., same LAN, rogue Wi-Fi, or upstream hop) passively captures the publish-visitor-session-id cookie during a Basic Auth exchange and replays it against the authenticated publish endpoints, gaining access without ever learning the account password. No public exploit code is identified, but the technique is a standard session-replay and requires no custom tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Authentication bypass in the SiYuan note-taking and knowledge-management publish service affects all releases before v3.8.4: session cookies for the publish feature are issued without the Secure or SameSite attributes and are transmitted over plaintext HTTP, so an on-path attacker can observe the publish-visitor-session-id cookie during a legitimate Basic Auth exchange and replay it against authenticated publish endpoints without knowing the account password. Exploitation requires the publish service to be enabled and protected by Basic Auth, the service to be reachable over cleartext HTTP rather than HTTPS, and the attacker to hold a man-in-the-middle network position (attack requirements: present in the CVSS 4.0 vector); serving the service over TLS removes the exposure entirely. No public exploit code was identified at time of analysis and there is no CISA KEV entry; the independent assessment rates this CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, a confidentiality-only impact, making it a genuine but conditionally exploitable bypass rather than an unconditionally high-risk flaw.
RemediationAI
Vendor-released patch: upgrade to SiYuan v3.8.4 or later, which fixes the cookie/session handling and adds credential-version binding so that changing an account password or deleting an account immediately invalidates existing publish sessions. The two upstream fix commits are https://github.com/siyuan-note/siyuan/commit/79d47867b106467c951475a9193455b48d1f3682 and https://github.com/siyuan-note/siyuan/commit/ff4d215f78a8d6e6db6052be18b5f9f4db9c7d68, and the advisory is at https://github.com/siyuan-note/siyuan/security/advisories/GHSA-7j37-4gq6-wm7m. On the affected versions the single most effective compensating control is to stop serving the publish service over plaintext HTTP: terminate TLS at a reverse proxy (or expose it only through a VPN/overlay such as WireGuard) so that the publish-visitor-session-id cookie can never be observed on the wire; the trade-off is added certificate management and, for VPN-only access, loss of anonymous public publishing. If TLS cannot be deployed immediately, restrict network reachability of the publish port with firewall rules or an IP allowlist so no attacker can obtain an on-path position, at the cost of limiting legitimate remote readers. Disabling the publish service entirely removes the attack surface but also removes the sharing functionality. Note that on unpatched versions, rotating the Basic Auth password is not a reliable way to invalidate an already-captured cookie, so password rotation alone should not be treated as remediation until the v3.8.4 upgrade is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is rooted in CWE-319 (Cleartext Transmission of Sensitive Information) combined with weak session-cookie hygiene in SiYuan's publish service, implemented in the Go source file kernel/model/auth.go. The publish feature supports HTTP Basic Auth accounts, and upon a successful credential exchange the server issues a session identifier (publish-visitor-session-id) that is later used to authorize requests to publish endpoints. Because that cookie was not marked Secure or SameSite and the service was commonly fronted by plain HTTP, the token traveled in cleartext and could be passively captured by anyone with network vantage between client and server. The v3.8.4 fix also addresses the session lifecycle: it introduces a CredentialVersion field on both Account and PublishSession, changes GetBasicAuthUsernameBySessionID into GetBasicAuthAccountBySessionID (returning nil when the session is missing, expired, or bound to a stale credential version), and makes AddSession refuse to create sessions for accounts whose credential version has changed. InitPublishAccounts now assigns a UUID credential version to each account and immediately deletes any session whose username no longer exists or whose credential version no longer matches, so password changes and account deletions actively revoke outstanding publish sessions. The CPE cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:* confirms the whole product line before the fix is affected, not a separate publishing component. Note the assessed vector limits impact to confidentiality (VC:H/VI:N/VA:N in the 4.0 vector; C:H/I:N/A:N in 3.1), consistent with an attacker reading content behind the publish authentication gate rather than modifying data or disrupting availability.
Know when Siyuan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
AC:H because exploitation requires an on-path position and a plaintext HTTP deployment to capture the cookie; PR:N as no attacker credentials are needed; C:H for full publish-session access, I/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
SiYuan before v3.8.4 contains an authentication bypass vulnerability in the publish service where session cookies are issued without Secure or SameSite attributes over plaintext HTTP connections. An on-path attacker can observe a valid publish-visitor-session-id cookie from a Basic Auth exchange and replay it to access authenticated publish endpoints without knowing the account password.
Technical POC Analysis
CWE-319 (cleartext transmission of sensitive information), with CWE-614 for the missing cookie attribute.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
SiYuan's publish service (all releases before v3.8.4) can expose published knowledge-base content to an on-path attacker through session-cookie replay when Basic Auth is used over cleartext HTTP. This confidentiality-only issue affects organizations that enable the publish feature without TLS, allowing unauthorized reading of published notes. Leadership should prioritize upgrading to v3.8.4 and enforcing HTTPS because the vendor patch is available and TLS removes the exposure entirely.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
SQL injection in SiYuan's fullTextSearchAssetContent endpoint lets unauthenticated attackers and holders of publish Role
Stored cross-site scripting in SiYuan personal knowledge management before 3.7.0 lets an attacker with write access to a
SQL injection in SiYuan personal knowledge management (versions <= v3.7.2) lets attackers pass arbitrary SQL statements
Stored cross-site scripting in SiYuan's attribute-view (database) cell renderer, affecting all versions prior to 3.7.0,
SQL injection in SiYuan personal knowledge-management software (all versions before v3.7.3) lets attackers inject arbitr
A SQL injection vulnerability was discovered in Siyuan 3.1.11 in /getHistoryItems. Rated critical severity (CVSS 9.8), t
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the ids array parameter in /batchGetBlockAttrs. R
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the id parameter at /getAssetContent. Rated criti
A SQL injection vulnerability has been identified in Siyuan 3.1.11 via the notebook parameter in /searchHistory. Rated c
SiYuan personal knowledge management system prior to 3.5.4 has a stored XSS vulnerability (CVSS 9.6) that allows code ex
Remote code execution in SiYuan note-taking application (before v3.6.1) allows any malicious Bazaar marketplace package
Origin-validation bypass in SiYuan Note (open-source personal knowledge management) before 3.7.0 lets any installed Chro
EUVD-2026-87729
GHSA-9f49-xx3h-chx9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB