Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-72807 high CVSS 8.0

SQL Injection in github.com/siyuan-note/siyuan/kernel (CVE-2026-72807)

Summary

SQL injection in github.com/siyuan-note/siyuan/kernel (CVE-2026-72807). Confidential information can be exposed externally. Exploitable via POST /api/filetree/createDocWithMd. Mitigation: upgrade to 0.0.0-20260723035036-0a176345e02a or later.

Original description

The description as published by the source.

CVE: This vulnerability corresponds to CVE-2026-72807.

Summary

Attribute-view (AV) template columns are live-evaluated on every render and expose the queryBlocks template function, which runs raw SQL on the read-write database handle (SelectBlocksRawStmt, using ?→argument string substitution rather than parameter binding). AV mutations are admin-gated, so this is not directly reader-injectable but it is a second-order vector: an attacker distributes a SiYuan document or AV package whose template column contains .action{queryBlocks ""} when a victim imports the package and renders the AV, the attacker's SQL executes on the victim's kernel (read and, via statement stacking, write).

Details

Doc-level {{…}} templates are rendered at insert-time and become static, so they are not re-evaluated on reader view. The residual is AV template columns, which are live-evaluated at render. queryBlocks passes its argument to SelectBlocksRawStmt with ?→arg string substitution, not a bound parameter, on the main read-write handle (88250/go-sqlite3 fork, statement-stacking capable) so an attacker-controlled template argument becomes arbitrary SQL.

The SSTI surface is otherwise hardened: BuiltInTemplateFuncs deletes env, expandenv, and getHostByName so there is no environment/host/file/exec SSTI. queryBlocks-to-SQL is the remaining live-evaluated sink.

Proof of Concept

An AV template column set…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-72807 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/filetree/createDocWithMd over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.0/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260723035036-0a176345e02a or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72807" on the vendor's site.

CVE-2026-72807 (github.com/siyuan-note/siyuan/kernel) — CWE-89 / CVSS v3 8.0
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /api/filetree/createDocWithMd / POST /api/av/renderAttributeView / queryBlocks / SelectBlocksRawStmt
Patched: 0.0.0-20260723035036-0a176345e02a — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/filetree/createDocWithMd without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/filetree/createDocWithMd / POST /api/av/renderAttributeView / queryBlocks / SelectBlocksRawStmt.

🔥 Severity

Severity: High (CVSS 8.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260723035036-0a176345e02a.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/filetree/createDocWithMd requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/siyuan-note/siyuan/kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/siyuan-note/siyuan/kernel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/siyuan-note/siyuan/kernel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/filetree/createDocWithMd' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/filetree/createDocWithMd への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260723035036-0a176345e02a

    ステージング環境で 0.0.0-20260723035036-0a176345e02a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/filetree/createDocWithMd on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/siyuan-note/siyuan/kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260723035036-0a176345e02a"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details