Skip to main content
VulnerabilityPublished Updated

CVE-2026-24399: chattermate.chat · Cross-site Scripting

Affects chattermate.chatSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.0.9 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jan 2026

  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

Upgrade chattermate.chat and chattermate/chattermate.chat to 1.0.9.

Affected software

ProductAffectedFixed in
chattermatechattermate.chatAffected
  • <1.0.9
Fixed in
  • 1.0.9
GitHubchattermate/chattermate.chatpkg:github/chattermate/chattermate.chatOther threatsAffected
  • <1.0.9
Fixed in
  • 1.0.9

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

AI-suggested

  1. Immediate upgrade to chattermate.chat version 1.0.9 or later, where the vulnerability is fixed.
  2. Implement strict input validation and output encoding on all user-supplied content, especially chat inputs, to prevent injection of malicious HTML or JavaScript.
  3. Employ Content Security Policy (CSP) headers to restrict execution of unauthorized scripts and iframe sources.
  4. Conduct user awareness training to recognize and avoid interacting with suspicious chat inputs or links.
  5. Monitor chat logs and user activity for signs of exploitation or anomalous behavior.
  6. Use web application firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting chattermate.chat.
  7. Regularly audit and test chatbot implementations for security weaknesses, including penetration testing focused on injection flaws.
  8. Isolate chatbot services from critical internal systems to limit potential lateral movement if compromised.

Description

ChatterMate is a no-code AI chatbot agent framework. In versions 1.0.8 and below, the chatbot accepts and executes malicious HTML/JavaScript payloads when supplied as chat input. Specifically, an <iframe> payload containing a javascript: URI can be processed and executed in the browser context. This allows access to sensitive client-side data such as localStorage tokens and cookies, resulting in client-side injection. This issue has been fixed in version 1.0.9.

References

Community reviews

Loading reviews…