logseq up to 0.10.15 package.json Name cross site scripting

Summaryinfo

A vulnerability described as problematic has been identified in logseq up to 0.10.15. Affected by this vulnerability is an unknown functionality of the file package.json. Executing a manipulation of the argument Name can lead to cross site scripting. This vulnerability is handled as CVE-2026-47900. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in logseq up to 0.10.15. It has been declared as problematic. This vulnerability affects an unknown code block of the file package.json. The manipulation of the argument name with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. CVE summarizes:

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.

The weakness was released by Bartłomiej Dmitruk. The advisory is shared for download at cert.pl. This vulnerability was named CVE-2026-47900 since 05/20/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.

By approaching the search of inurl:package.json it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• logseq

Version

• 0.10.0
• 0.10.1
• 0.10.2
• 0.10.3
• 0.10.4
• 0.10.5
• 0.10.6
• 0.10.7
• 0.10.8
• 0.10.9
• 0.10.10
• 0.10.11
• 0.10.12
• 0.10.13
• 0.10.14
• 0.10.15

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion