CVE-2026-54070
HIGHDescription
SiYuan is an open-source personal knowledge management system. Prior to 3.7.0, renderPackageREADME in kernel/bazaar/readme.go renders a Bazaar package README from Markdown to HTML with the lute engine and SetSanitize(true). The lute sanitizer is an event-handler blocklist: allowAttr rejects only attribute names present in a fixed eventAttrs map copied from the w3schools legacy handler list. That map omits modern event handlers. onpointerover, onpointerdown, onauxclick, onbeforetoggle, onfocusin, onanimationstart, and ontransitionend are not in the list, so the sanitizer passes them through verbatim on any tag. The frontend assigns the rendered HTML to mdElement.innerHTML in app/src/config/bazaar.ts with no client-side DOMPurify on this path, into a normal element in the main document (no iframe, no sandbox). The kernel sends no Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options header on any response, so an inline handler runs when its event fires. The README is rendered when an Administrator opens a package in Settings → Marketplace, after the one-time marketplace trust consent. Install is not required. Result: a third-party Bazaar package author runs JavaScript in the Administrator's authenticated SiYuan origin when the Administrator views and interacts with the package listing, and gains full control of the workspace. This vulnerability is fixed in 3.7.0.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 22% of all known CVEs.
References
Related Vulnerabilities
Other CWE-79 (Cross-Site Scripting (XSS)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-12998 | Medium | 6.1 | 99% | - | - |
| CVE-2020-11022 | Medium | 6.9 | 99% | - | Fix |
| CVE-2019-3929 | Critical | 9.8 | 99% | KEV | Fix |
| CVE-2020-9496 | Medium | 6.1 | 99% | - | - |
| CVE-2023-28341 | Medium | 6.1 | 99% | - | Fix |
| CVE-2021-25299 | Medium | 6.1 | 98% | - | - |
Common questions
How do I fix CVE-2026-54070?
No published fix for CVE-2026-54070 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54070 being actively exploited?
Not that we know of. CVE-2026-54070 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 22% of all scored CVEs.
How severe is CVE-2026-54070?
CVE-2026-54070 has a CVSS v3 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54070
Markdown
[](https://tridentstack.com/cve/CVE-2026-54070)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54070"><img src="https://tridentstack.com/cve/badge/CVE-2026-54070.svg" alt="CVE-2026-54070"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-26.