The Telegram Bot & Channel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Telegram username
Source GCVE Database
Not known to be exploited · CVSS 7.2 High.
Data as of 18 Nov 2026, 02:28 UTC
- Affects
- all up to 4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
AI-suggested
Until a fix is available, consider restricting or validating Telegram username inputs manually or applying web application firewall rules to detect and block malicious script payloads targeting this plugin.
Description
The Telegram Bot & Channel plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in all versions up to and including 4.1. This vulnerability arises from insufficient input sanitization and output escaping of the Telegram username, allowing unauthenticated attackers to inject arbitrary scripts that execute when users access affected pages.