LobeHub up to 2.1.47 IPC Interface index.tsx cross site scripting

Summaryinfo

A vulnerability was found in LobeHub up to 2.1.47. It has been rated as problematic. Affected is an unknown function of the file src/features/Portal/Artifacts/Body/Renderer/index.tsx of the component IPC Interface. This manipulation causes cross site scripting. This vulnerability is tracked as CVE-2026-42045. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in LobeHub up to 2.1.47 and classified as problematic. Affected by this vulnerability is an unknown function of the file src/features/Portal/Artifacts/Body/Renderer/index.tsx of the component IPC Interface. The manipulation 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. The summary by CVE is:

LobeHub is a work-and-lifestyle space to find, build, and collaborate with agent teammates that grow with you. Prior to 2.1.48, when LobeChat processes custom tags in the Render process of src/features/Portal/Artifacts/Body/Renderer/index.tsx, if no type match is found, it will choose to call the default method, HTMLRenderer, for HTML rendering. If an attacker can induce the LLM to output content containing malicious tags, an XSS vulnerability can be created on the client side. Additionally, Lobechat's Electron main process exposes an IPC interface called runCommand, used to invoke system commands. This interface allows arbitrary command execution and does not filter the command parameter. Therefore, if an attacker can obtain a handle to window.parent.electronAPI via XSS and call the runCommand method of the IPC, the ipcMain process can execute arbitrary system commands with the current user's privileges. This vulnerability is fixed in 2.1.48.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-42045 since 04/23/2026. The exploitation appears to be difficult. The attack can be launched remotely. Additional levels of successful authentication are required for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

Upgrading to version 2.1.48 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• LobeHub

Version

• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 2.1.6
• 2.1.7
• 2.1.8
• 2.1.9
• 2.1.10
• 2.1.11
• 2.1.12
• 2.1.13
• 2.1.14
• 2.1.15
• 2.1.16
• 2.1.17
• 2.1.18
• 2.1.19
• 2.1.20
• 2.1.21
• 2.1.22
• 2.1.23
• 2.1.24
• 2.1.25
• 2.1.26
• 2.1.27
• 2.1.28
• 2.1.29
• 2.1.30
• 2.1.31
• 2.1.32
• 2.1.33
• 2.1.34
• 2.1.35
• 2.1.36
• 2.1.37
• 2.1.38
• 2.1.39
• 2.1.40
• 2.1.41
• 2.1.42
• 2.1.43
• 2.1.44
• 2.1.45
• 2.1.46
• 2.1.47

Website

• Product: https://github.com/lobehub/lobehub/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion