# CVE-2026-47900: Logseq stored XSS in plugin package.json name field

Source: https://junglewise.ai/threats/cve-2026-47900-logseq-stored-xss-in-plugin-package-json-name-field  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-09. Updated: 2026-06-09  
License: CC BY 4.0 with a link back

CVE-2026-47900 · Severity: info · CVSS 4.6 · Published 2026-06-09

Logseq, a popular open-source knowledge management and note-taking application, is vulnerable to a security flaw involving its plugin system. A malicious plugin can execute unauthorized code on a user's computer by hiding a script within its configuration file. If a user installs such a plugin, an attacker could potentially gain control over the application and access or modify the user's private notes and data.

Technologies: [Logseq](https://junglewise.ai/threats/technologies/logseq). Vendors: [Logseq](https://junglewise.ai/threats/vendors/logseq).

## Quick answers

**Is CVE-2026-47900 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-47900 being exploited in the wild.

**How severe is CVE-2026-47900?** Informational severity, with a CVSS score of 4.6, published 9 June 2026.

**Which products and versions are affected?** Logseq All through 0.10.15.

**Is there a fix for CVE-2026-47900?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-47900 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2026-47900?** Check whether you run Logseq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A stored cross-site scripting (XSS) vulnerability exists in Logseq due to improper sanitization of plugin metadata. Specifically, the 'name' field within a plugin's 'package.json' file is rendered using the 'innerHTML' property without adequate neutralization. An attacker can craft a malicious plugin containing a JavaScript payload in this field. When the plugin is processed or displayed by the application, the payload executes in the privileged host context. This can be further chained with other reported vulnerabilities in the application's IPC handlers to achieve arbitrary shell command execution or unauthorized filesystem access. As of the advisory date, no patch has been released by the vendor.

## Affected products

- Logseq Logseq All through 0.10.15

## Timeline

- 2026-06-09: disclosed: Vulnerability disclosed by CERT Polska
- 2026-06-09: advisory: CVE-2026-47900 published

## References

- [https://cert.pl/en/posts/2026/06/CVE-2026-9279/](https://cert.pl/en/posts/2026/06/CVE-2026-9279/)
- [https://logseq.com/](https://logseq.com/)

## Related threats

- [Logseq missing authentication in Local HTTP API](https://junglewise.ai/threats/cve-2026-124573-a-vulnerability-was-found-in-logseq-2-0-1-2-0-2-this-affects-the)
- [Logseq OS command injection in IPC handler](https://junglewise.ai/threats/cve-2026-9279-logseq-os-command-injection-in-ipc-handler)
- [Logseq sandbox escape via plugin HTML attribute injection](https://junglewise.ai/threats/cve-2026-47901-logseq-sandbox-escape-via-plugin-html-attribute-injection)
- [Logseq exposed dangerous IPC method in Electron preload script](https://junglewise.ai/threats/cve-2026-47899-logseq-exposed-dangerous-ipc-method-in-electron-preload-script)