Skip to main content
VulnerabilityPublished

CVE-2026-54681: Tyrrrz DiscordChatExporter · Cross-site Scripting

Affects Tyrrrz DiscordChatExporterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.1 Medium : upgrade to 2.47.2 when convenient.

Data as of 19 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 19 Nov 2026.

What to do

Upgrade DiscordChatExporter and tyrrrz/DiscordChatExporter to 2.47.2.

Affected software

ProductAffectedFixed in
TyrrrzDiscordChatExporterAffected
  • <2.47.2
Fixed in
  • 2.47.2
GitHubtyrrrz/DiscordChatExporterpkg:github/tyrrrz/DiscordChatExporterOther threatsAffected
  • <2.47.2
Fixed in
  • 2.47.2

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

AI-suggested

Upgrade DiscordChatExporter to version 2.47.2 or later where this issue is fixed. Until then, avoid opening exported HTML files from untrusted or tampered sources.

Description

DiscordChatExporter saves Discord chat logs to a file. Prior to 2.47.2, the VisitEmojiAsync method in DiscordChatExporter.Core/Exporting/HtmlMarkdownVisitor.cs interpolates emoji.Name into the alt attribute and emoji.Code into the title attribute without HTML entity encoding. This affects HTML exports regardless of the markdown setting. Discord's current custom emoji name validation normally excludes attribute-breaking characters, but tampered offline input, a relaxed upstream validation rule, or another future metadata source can inject an HTML attribute and execute script when a user opens the export. This issue is fixed in version 2.47.2.

References

Community reviews

Loading reviews…