Stored XSS via Unsanitized Plugin Metadata in Logseq
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Active
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
Logseq is vulnerable to a stored cross-site scripting (XSS). A malicious plugin can include a JavaScript payload in the "name" field of its "package.json" file, which is rendered using "innerHTML" without proper sanitization, allowing the execution of arbitrary code in the privileged host context. While only version v0.10.15 was tested and confirmed as vulnerable, status of other versions is unknown since this issue was not addressed by a patch.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-47900
- 2026-10-03 Alias added: GHSA-fff3-7r5v-99cq
References
Other 1
More logseq vulnerabilities
- TI-2026-08151 Shell command injection in Logseq CVSS 4.0HIGH 8.7
- TI-2026-35347 Arbitrary File Read, Write, Rename, and Delete in Logseq CVSS 4.0HIGH 8.7
- TI-2026-35349 Iframe escape by plugins in Logseq CVSS 4.0MEDIUM 4.6
Sources
- CVE-2026-47900 · CVE Program
- CVE-2026-47900 · NVD
- FIRST EPSS
- GHSA-fff3-7r5v-99cq · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences