Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Back to vulnerabilities
Medium

Stored XSS in Logseq plugin package.json name field

IdentifiersCVE-2026-47900CWE-79· Improper Neutralization of Input…

Logseq contains a stored cross-site scripting vulnerability in its plugin handling. A malicious plugin can place a JavaScript payload in the "name" field of its "package.json" metadata. Logseq renders that plugin name using "innerHTML" without proper sanitization, causing attacker-controlled HTML/JavaScript to be injected into the application UI. Because the injected script executes in the privileged host context rather than an isolated renderer sandbox, successful exploitation can lead beyond ordinary DOM-based XSS to arbitrary code execution within the Logseq application context. The provided reporting states that version 0.10.15 was tested and confirmed vulnerable; the status of other versions is unknown because no patch had addressed the issue at the time of disclosure.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation gives an attacker arbitrary JavaScript execution in Logseq's privileged host context. In practice, this can compromise the confidentiality and integrity of data accessible to the application and may enable further abuse of privileged application capabilities, including escalation to arbitrary code execution within the host application context. In environments where Logseq exposes sensitive local resources or privileged APIs, this can result in broader compromise of the user's application environment.

Mitigation

If you can’t patch tonight, do this now.

Do not install untrusted or third-party plugins from unverified sources. Restrict plugin installation to trusted, reviewed packages only. Where possible, disable plugin functionality or remove suspicious plugins until a fix is available. Additional hardening should include enforcing stronger isolation between plugin content and privileged host context and enabling defensive browser controls such as an effective Content Security Policy where applicable, though the provided content does not specify a vendor-supported mitigation beyond avoiding untrusted plugins.

Remediation

Patch, then assume compromise.

Sanitize or safely encode plugin metadata before rendering, and stop inserting untrusted plugin fields such as "package.json" "name" values via "innerHTML". Render the value as text content or use a vetted HTML sanitization library if HTML rendering is absolutely required. Review all plugin metadata rendering paths for equivalent unsafe DOM sinks. Update to a vendor-fixed release if one becomes available; the provided content does not identify a released patch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LogseqLogseqapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

1 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-47900
NVD
nvd.nist.gov/vuln/detail/CVE-2026-47900
MITRE CWE · CWE-79
Improper Neutralization of Input During Web…
cert.pl
cert.pl/en/posts/2026/06/CVE-2026-9279
logseq.com
logseq.com