# CVE-2026-47900: Stored XSS via Unsanitized Plugin Metadata in Logseq

> A malicious plugin can execute arbitrary code in Logseq by injecting JavaScript into its package name, which is rendered without sanitization.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-fff3-7r5v-99cq

## What is CVE-2026-47900?

CVE-2026-47900 is a medium-severity cross-site scripting vulnerability in logseq, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-47900?


## How do I fix CVE-2026-47900?

No fix has been published for CVE-2026-47900 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47900 being exploited?

There is no known exploitation of CVE-2026-47900 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47900 and fix it if it is affected.

What it is: CVE-2026-47900 is a medium-severity cross-site scripting vulnerability in logseq, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47900 in the wild and no public exploit code.

Affected product: logseq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47900/ (Markdown: https://insights.sbomify.com/CVE-2026-47900/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47900
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47900
- OSV: https://osv.dev/vulnerability/CVE-2026-47900

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47900/
Summaries are generated and may contain mistakes; the official description above is the record.