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

Logseq sandbox escape via plugin HTML attribute injection

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

Logseq is affected by a sandbox escape vulnerability in which plugins running inside sandboxed iframes can inject arbitrary HTML attributes, including JavaScript event-handler attributes, into their container element in the host DOM. Because Content Security Policy protections are disabled, those injected attributes can be used to execute arbitrary JavaScript in the privileged host context rather than remaining confined to the sandboxed plugin frame. The issue was reported as affecting Logseq through version 0.10.15; the provided content states that v0.10.15 was tested and confirmed vulnerable, while the status of other versions is unknown because no patch had addressed the issue.

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.

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 allows a malicious plugin to break out of the intended iframe sandbox boundary and execute arbitrary JavaScript in Logseq's privileged host context. This can lead to unauthorized access to filesystem APIs and potentially broader compromise of data and actions available to the Logseq application context.

Mitigation

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

No vendor-provided workaround is described in the provided content. As an interim mitigation, avoid installing or running untrusted plugins, restrict plugin usage to trusted sources only, and disable or limit plugin functionality where operationally feasible until a fix is available.

Remediation

Patch, then assume compromise.

No patch or fixed version is described in the provided content. The vendor had not addressed the issue at the time of disclosure. Organizations should monitor for an official vendor update and apply it once available.
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.

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.
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.