Is Notification for Telegram safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.5.5). As of 2026-11-04. 6 issues are on record for older versions; version 3.5.3 or newer fixes all of them that state a fix. Keep Notification for Telegram on the latest version (3.5.5) and remove it if you do not use it.

Which versions of Notification for Telegram are vulnerable?

Known issues on record (newest first): Cross-site scripting (XSS) (3.5.2 and older, fixed in 3.5.3); Missing authorization check (3.5.1 and older, fixed in 3.5.2); Cross-site scripting (XSS) (3.5 and older, fixed in 3.5.1); Cross-site request forgery (CSRF) (3.5 and older, fixed in 3.5.1); Missing authorization check (3.3.1 and older, fixed in 3.3.2). The full list with sources is on this page.

What is the latest version of Notification for Telegram?

3.5.5, according to wordpress.org (last updated 2026-09-18). It has 4,000+ active installs.

What should I do if my Notification for Telegram is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update notification-for-telegram). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · notification-for-telegram · data as of 2026-11-04

Is Notification for Telegram safe? Known vulnerabilities and latest version

Latest version: 3.5.5
Last updated: 2026-09-18
Active installs: 4,000+
Known issues on record: 6
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

Sends notifications to Telegram users or groups, when some events occur in WordPress. — by rainafarai

What to do

Update to the latest version (3.5.5). Anything older than 3.5.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get notification-for-telegram --field=version shows what you run; wp plugin update notification-for-telegram updates it.

Check your version

Known vulnerabilities

6 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.1 CVE-2026-93514 · published 2026-09-30

Cross-site scripting (XSS) in Notification for Telegram (3.5.2 and older)

Affected: 3.5.2 and older
Fixed in: 3.5.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Cross Site Scripting (XSS) in Notification for Telegram <= 3.5.2 versions.

NVD CVE-2026-93514 Patchstack advisory

medium 4.3 CVE-2026-7620 · published 2026-07-11

Missing authorization check in Notification for Telegram (3.5.1 and older)

Affected: 3.5.1 and older
Fixed in: 3.5.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Notification for Telegram plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.5.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to create, modify, or reschedule the nftb_cron_hook WordPress cron event, enabling unauthorized manipulation of the plugin's background task scheduling logic.

NVD CVE-2026-7620 Wordfence advisory Code change (fix)Plugin source

high 7.1 CVE-2026-40732 · published 2026-06-15

Cross-site scripting (XSS) in Notification for Telegram (3.5 and older)

Affected: 3.5 and older
Fixed in: 3.5.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Cross Site Scripting (XSS) in Notification for Telegram <= 3.5 versions.

NVD CVE-2026-40732 Patchstack advisory

medium 4.3 CVE-2025-62993 · published 2025-12-09

Missing authorization check in Notification for Telegram (3.5.1 and older)

Affected: 3.5.1 and older
Fixed in: 3.5.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in rainafarai Notification for Telegram notification-for-telegram allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Notification for Telegram: from n/a through <= 3.5.1.

NVD CVE-2025-62993 Patchstack advisory

medium 4.3 CVE-2025-58794 · published 2025-09-05

Cross-site request forgery (CSRF) in Notification for Telegram (3.5 and older)

Affected: 3.5 and older
Fixed in: 3.5.1 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in rainafarai Notification for Telegram notification-for-telegram allows Cross Site Request Forgery.This issue affects Notification for Telegram: from n/a through <= 3.5.

NVD CVE-2025-58794 Patchstack advisory

medium 4.3 CVE-2024-9685 · published 2024-10-10

Missing authorization check in Notification for Telegram (3.3.1 and older)

Affected: 3.3.1 and older
Fixed in: 3.3.2 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nftb_test_action' function in versions up to, and including, 3.3.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to send a test message via the Telegram Bot API to all users configured in the settings.

NVD CVE-2024-9685 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-09-18 — latest release on wordpress.org (3.5.5).
2026-09-30 — Cross-site scripting (XSS) disclosed (CVE-2026-93514), fixed in 3.5.3.
2026-07-11 — Missing authorization check disclosed (CVE-2026-7620), fixed in 3.5.2.
2026-06-15 — Cross-site scripting (XSS) disclosed (CVE-2026-40732), fixed in 3.5.1.

Free. We check the CVE feeds every day and email you only when a new issue for Notification for Telegram (notification-for-telegram) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (3) · Cross-site scripting (XSS) (2) · Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/notification-for-telegram (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/notification-for-telegram"><img src="https://laskyr.com/plugins/notification-for-telegram/badge.svg" alt="Notification for Telegram vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Notification for Telegram safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.5.5)

What to do

Check your version

Known vulnerabilities

Cross-site scripting (XSS) in Notification for Telegram (3.5.2 and older)

Missing authorization check in Notification for Telegram (3.5.1 and older)

Cross-site scripting (XSS) in Notification for Telegram (3.5 and older)

Missing authorization check in Notification for Telegram (3.5.1 and older)

Cross-site request forgery (CSRF) in Notification for Telegram (3.5 and older)

Missing authorization check in Notification for Telegram (3.3.1 and older)

Recent activity

Get an email when Notification for Telegram has a new vulnerability

Browse vulnerabilities

Where this data comes from