dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-54068

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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, the /api/icon/getDynamicIcon endpoint is explicitly excluded from authentication in SiYuan's kernel router (router.go, "不需要鉴权" -- no auth needed). When called with type=8 and a valid block id parameter, this endpoint invokes RenderDynamicIconContentTemplate, which executes a Go template that includes the querySQL and queryBlocks functions. These functions run arbitrary SELECT statements against the SiYuan SQLite database. An unauthenticated network-adjacent attacker who knows a valid block ID can exfiltrate all user note content, tags, asset references, and block attributes from the database. 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's /api/icon/getDynamicIcon endpoint is explicitly excluded from authentication. When called with type=8 and a valid block ID, it executes Go templates containing querySQL and queryBlocks functions that run arbitrary SELECT statements against the SQLite database, allowing unauthenticated network-adjacent attackers to exfiltrate all user note content, tags, assets, and block attributes.

MitigationUpgrade to SiYuan version 3.7.0 or later to patch this authentication bypass vulnerability.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm SiYuan is installed
    Look for SiYuan application files, processes, or check running services on the system. Common locations: /opt/siyuan, %APPDATA%/siyuan, or the installation directory.
    Affected if SiYuan software is present and running on the system
  2. Identify SiYuan version
    Check the version number of the installed SiYuan instance. Typically found in the application, config file, or by querying the API. Compare against the affected version range (before 3.7.0).
    Affected if The installed version is earlier than 3.7.0
  3. Verify API endpoint accessibility
    Attempt to access the /api/icon/getDynamicIcon endpoint without providing authentication credentials. Send a request to this endpoint and observe if it responds without requiring login.
    Affected if The endpoint responds to unauthenticated requests
  4. Test for template injection parameter
    Send a request to /api/icon/getDynamicIcon with type=8 parameter and a valid block ID. Observe if the response includes processed Go template content indicating the querySQL or queryBlocks functions are being executed.
    Affected if The endpoint accepts type=8 and returns data derived from template execution against the database

A SiYuan installation is affected if it is version 3.6.x or earlier and the unauthenticated /api/icon/getDynamicIcon endpoint with type=8 parameter is accessible and returns database query results.

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 version 3.7.0 or later to patch this authentication bypass vulnerability.

Recommended fix High confidence

3.7.0

  1. 1. Back up your existing SiYuan data directory before upgrading
  2. 2. Download SiYuan version 3.7.0 from the official GitHub releases page (github.com/siyuan-note/siyuan)
  3. 3. Install or update to the downloaded version 3.7.0
  4. 4. Verify the installation by checking the application version
  5. 5. Test that the /api/icon/getDynamicIcon endpoint now requires authentication
Caveat Review release notes for any configuration or data migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54068 — 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-54068 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