Privileged JavaScript execution via unsanitized plugin name
Published Jun 9, 2026 · Updated Jun 9, 2026
Stored XSS in Logseq 0.10.15 allows local users to execute JavaScript in the privileged host context through a malicious plugin. The plugin manager reads the name field from package.json and assigns it to innerHTML without sanitization, so script-bearing markup executes in the host DOM. Loading the attacker-controlled plugin requires active user interaction; execution remains in the Logseq process context unless chained with a separate host-escape flaw.
Summary
What happened
Stored XSS in Logseq 0.10.15 allows local users to execute JavaScript in the privileged host context through a malicious plugin. The plugin manager reads the name field from package.json and assigns it to innerHTML without sanitization, so script-bearing markup executes in the host DOM. Loading the attacker-controlled plugin requires active user interaction; execution remains in the Logseq process context unless chained with a separate host-escape flaw.
The record
- CVE
- CVE-2026-47900
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Logseq
- Product
- Logseq
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.10.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo