Skip to main content
VulnerabilityPublished

CVE-2025-66481: ThinkInAIXYZ deepchat · Basic XSS

Affects ThinkInAIXYZ deepchatSource CVE Database V5

0

Not known to be exploited · CVSS 9.7 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubthinkinaixyz/deepchatpkg:github/thinkinaixyz/deepchatOther threatsAffected
  • <=0.5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately disable or restrict rendering of Mermaid content within DeepChat to prevent injection vectors.
  2. Implement strict input validation and sanitization on all user-supplied content, especially focusing on unquoted HTML attributes and entity encoding.
  3. Employ Content Security Policy (CSP) headers to limit script execution sources and reduce XSS impact.
  4. Run DeepChat within isolated environments or sandboxes to contain potential RCE effects.
  5. Monitor network and endpoint logs for suspicious activity related to electron.ipcRenderer usage or anomalous script execution.
  6. Educate users to avoid interacting with untrusted or unexpected chat content until a patch is released.
  7. Engage with the DeepChat community or vendor to track patch developments and apply updates promptly once available.
  8. Consider alternative AI chat platforms with verified security postures if immediate risk reduction is critical.
  9. Conduct penetration testing and code audits focusing on HTML sanitization and Electron IPC interfaces.
  10. Use endpoint protection solutions capable of detecting and blocking malicious script execution and IPC abuse.

Description

DeepChat is an open-source AI chat platform that supports cloud models and LLMs. Versions 0.5.1 and below are vulnerable to XSS attacks through improperly sanitized Mermaid content. The recent security patch for MermaidArtifact.vue is insufficient and can be bypassed using unquoted HTML attributes combined with HTML entity encoding. Remote Code Execution is possible on the victim's machine via the electron.ipcRenderer interface, bypassing the regex filter intended to strip dangerous attributes. There is no fix at time of publication.

References

Community reviews

Loading reviews…