SiYuan versions <= v3.7.2 contain a SQL injection vulnerability in the backlink/mention search query (kernel/model/backlink.go), which concatenates stored block metadata (title, name, alias, anchor text) and the client-supplied keyword into a SQL MATCH/search statement while escaping only the double-quote character and not the single quote. A single quote in the client keyword (first-order, reachable by an anonymous or RoleReader user on the publish surface) or in stored document metadata (second-order) breaks out of the string literal. Because the query runs on the main read-write siyuan.db handle via a statement-stacking-capable driver, an attacker can execute arbitrary SQL, enabling cross-notebook read and write. Fixed in v3.7.4.
CVE-2026-72811
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-14. the CNA's CVSS baseline 10.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 10.0
- EG Score
- 10.0(high)
- EG Risk
- 60(Track)EG Risk 60/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity100% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 14, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 14, 2026SiYuan before v3.7.4 SQL Injection via backlink search | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-sql-injection-via-backlink-searchSQL injection in backlink/mention search via unescaped stored and client input (publish mode): first-order (client keyword) and second-order (stored document title) breakout on read-write handle · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-q2vg-7qgx-x5fcVendor Advisories for CVE-2026-72811(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 62× in last 7d / 62× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 06:07 UTCGHSA enrichment
- 2026-08-21 02:09 UTCEG score recompute
- 2026-08-21 02:09 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 22:11 UTCGHSA enrichment
- 2026-08-20 18:14 UTCGHSA enrichment
- 2026-08-20 14:16 UTCGHSA enrichment
- 2026-08-20 10:17 UTCGHSA enrichment
- 2026-08-20 06:20 UTCGHSA enrichment
- 2026-08-20 02:22 UTCGHSA enrichment
- 2026-08-19 22:24 UTCGHSA enrichment
- 2026-08-19 18:26 UTCEG score recompute
- 2026-08-19 18:26 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:04 UTCGHSA enrichment
- 2026-08-19 09:06 UTCGHSA enrichment
- 2026-08-19 05:06 UTCGHSA enrichment
- 2026-08-19 00:59 UTCGHSA enrichment
- 2026-08-18 21:01 UTCGHSA enrichment
- 2026-08-18 17:04 UTCEG score recompute
- 2026-08-18 17:03 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 12:41 UTCGHSA enrichment
- 2026-08-18 08:25 UTCGHSA enrichment
Show 37 moreShow fewer
- 2026-08-18 04:25 UTCGHSA enrichment
- 2026-08-18 00:27 UTCGHSA enrichment
- 2026-08-17 20:26 UTCGHSA enrichment
- 2026-08-17 16:28 UTCEG score recompute
- 2026-08-17 16:28 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:29 UTCGHSA enrichment
- 2026-08-17 08:31 UTCGHSA enrichment
- 2026-08-17 04:34 UTCGHSA enrichment
- 2026-08-17 00:36 UTCGHSA enrichment
- 2026-08-16 20:38 UTCGHSA enrichment
- 2026-08-16 16:40 UTCEG score recompute
- 2026-08-16 16:40 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:42 UTCGHSA enrichment
- 2026-08-16 08:44 UTCGHSA enrichment
- 2026-08-16 04:47 UTCEG score recompute
- 2026-08-16 04:47 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-16 00:49 UTCGHSA enrichment
- 2026-08-15 20:51 UTCGHSA enrichment
- 2026-08-15 16:53 UTCGHSA enrichment
- 2026-08-15 12:55 UTCGHSA enrichment
- 2026-08-15 08:57 UTCGHSA enrichment
- 2026-08-15 04:59 UTCGHSA enrichment
- 2026-08-15 01:01 UTCGHSA enrichment
- 2026-08-14 21:04 UTCGHSA enrichment
- 2026-08-14 17:06 UTCEG score recompute
- 2026-08-14 17:06 UTCGHSA enrichment
- 2026-08-14 16:31 UTCEG score recompute
- 2026-08-14 16:31 UTCGHSA enrichment
- 2026-08-14 15:39 UTCEG score recompute
- 2026-08-14 15:39 UTCGHSA enrichment
- 2026-08-14 12:22 UTCEG score recompute
- 2026-08-14 11:49 UTCEG score recompute
- 2026-08-14 11:49 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-72811?
When was CVE-2026-72811 disclosed?
Is CVE-2026-72811 actively exploited?
What is the CVSS score of CVE-2026-72811?
How do I remediate CVE-2026-72811?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72811
Is Your Infrastructure Affected by CVE-2026-72811?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.