CVE-2026-40732: Notification for Telegram (WordPress plugin) · Cross-site Scripting
Affects Notification for Telegram (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% 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:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rainafaraiNotification for Telegram | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, consider applying temporary mitigations such as input validation and output encoding on user-supplied data if possible. Monitor vendor channels for updates and apply patches promptly once released.
Description
CVE-2026-40732 is a high-severity vulnerability in Notification for Telegram by rainafarai, affecting versions up to and including 3.5. It is an unauthenticated Cross-Site Scripting (XSS) flaw that allows improper neutralization of input during web page generation. The vulnerability can lead to partial compromise of confidentiality, integrity, and availability. No official patch or remediation guidance is currently provided by the vendor.