dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-45371

HIGH · 7.2 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, SiYuan publish-mode Reader can mutate Conf and SQL index via 8 ungated APIs. POST /api/graph/getGraph, POST /api/graph/getLocalGraph, POST /api/sync/setSyncInterval, POST /api/storage/updateRecentDocViewTime, POST /api/storage/updateRecentDocCloseTime, POST /api/storage/updateRecentDocOpenTime, POST /api/storage/batchUpdateRecentDocCloseTime, and POST /api/search/updateEmbedBlock are registered with model.CheckAuth only, omitting both model.CheckAdminRole and model.CheckReadonly. Each of them writes server-side state, including atomic rewrites of <workspace>/conf/conf.json via model.Conf.Save(). Any caller whose JWT passes CheckAuth, including a publish-service RoleReader (the role assigned to anonymous publish visitors) and a RoleEditor against a workspace where Editor.ReadOnly = true, can hit them This vulnerability is fixed in 3.7.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SiYuan prior to 3.7.0 has 8 APIs (graph, sync, storage, and search endpoints) registered with only CheckAuth authentication validation, missing both CheckAdminRole and CheckReadonly authorization checks. This allows any authenticated user—including publish-service RoleReader (anonymous visitors) or RoleEditor with ReadOnly=true—to write server-side state including atomic rewrites of the conf.json configuration file.

MitigationUpgrade to SiYuan 3.7.0 or later which adds proper CheckAdminRole and CheckReadonly authorization checks to these endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SiYuan installation and version
    Locate the SiYuan application and determine its installed version number. This is typically found in the application metadata, about dialog, or installation directory.
    Affected if The installed version is lower than 3.7.0 (e.g., 3.6.x, 3.5.x, etc.)
  2. Check if publish service is enabled
    Inspect the SiYuan configuration to determine if the publish-service feature is active, which allows RoleReader (anonymous) access.
    Affected if Publish service is enabled and exposes APIs to unauthenticated visitors
  3. Verify user role configuration
    Review the user accounts and their assigned roles in the SiYuan system, specifically looking for RoleEditor accounts with ReadOnly=true or any RoleReader accounts.
    Affected if Non-admin authenticated users exist with limited roles or read-only status
  4. Confirm API endpoint exposure
    Identify if the graph, sync, storage, or search API endpoints are accessible over the network or locally.
    Affected if These eight APIs (graph, sync, storage, search endpoints) are reachable without admin privileges
  5. Test API authorization behavior
    Attempt to make a write request to one of the affected APIs (graph, sync, storage, or search endpoints) using a non-admin or read-only account.
    Affected if The request succeeds and modifies server-side state (such as conf.json) without proper authorization failure

You are affected if SiYuan version is below 3.7.0 AND either publish service is enabled, non-admin users exist, or write operations succeed on restricted APIs without proper admin/read-only authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SiYuan 3.7.0 or later which adds proper CheckAdminRole and CheckReadonly authorization checks to these endpoints.

Recommended fix High confidence

3.7.0

  1. Backup your SiYuan workspace data and configuration files before upgrading
  2. Check your current SiYuan version to confirm it is prior to 3.7.0
  3. Download SiYuan version 3.7.0 from the official GitHub releases page (github.com/siyuan-note/siyuan/releases)
  4. Stop the SiYuan service before applying the upgrade
  5. Install or replace the SiYuan application with version 3.7.0
  6. Restart the SiYuan service
  7. Verify the installation by checking the version number and testing that the affected APIs now properly enforce admin role and read-only checks

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data