Notification for Telegram
Healthy: released 48 days ago, tested with WordPress 7.1, no open vulnerabilities.
Based on 3 of 5 areas
| Ownership | 100 |
|---|---|
| Maintenance | 100 |
| Security | 65 |
| Support | No data |
| Reputation | No data |
Active signals
Open issues right now, with links to the source.
- InfoSEC-35 vulnerabilities published in the last 24 months. Review this plugin.4 Nov 2026Evidence
History: 6 past vulnerabilities, all patched. Patched issues are listed in the Security record, not here.
Quick answers
- Is Notification for Telegram still maintained?
- Yes. Last release 18 Sep 2026, 18 releases in the last 24 months. 18 Sep 2026 · wordpress.org
- Who owns Notification for Telegram, and has it changed hands?
- No change recorded. Main committer rainafarai since Sep 2020. 3 Nov 2026 · SVN log
- Was Notification for Telegram removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is Notification for Telegram safe?
- 6 known vulnerabilities, all fixed (latest in 3.5.3). Not on the exploited list. 28 Sep 2026 · Wordfence Intelligence
- Is the latest Notification for Telegram update safe to install?
- No ownership change before 3.5.5. No one-star spike after it. 18 Sep 2026 · Release history
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 16 Sep 2020 to 16 Sep 2020, 1 commits |
|---|---|
| rainafarai | 17 Sep 2020 to 18 Sep 2026, 127 commits |
2 committers recorded. No ownership changes recorded since 2020.
Maintenance
- Last release
- 48 days ago
- Releases, 24 months
- 18
- Tested up to
- 7.1 current
- Requires PHP
- 7.4 supported 8.2+
| Q1 2024 | 1 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 3 |
| Q1 2025 | 4 |
| Q2 2025 | 1 |
| Q3 2025 | 6 |
| Q4 2025 | 1 |
| Q1 2026 | 1 |
| Q2 2026 | 2 |
| Q3 2026 | 2 |
| Q4 2026 | 0 |
Last release 18 Sep 2026. Tested with WordPress 7.1 (current).
Support
- Resolved, last 2 months
- 100%
- Threads, last 2 months
- 1
Trend appears after 8 weekly snapshots.
Security record
5 vulnerabilities in 24 months (6 on record), all patched (latest fixed in 3.5.3).
Show 6 patched vulnerabilities
| Date | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 28 Sep 2026 | Unauthenticated Stored Cross-Site Scripting | 7.2 | <= 3.5.2 | 3.5.3 | Before disclosure |
| 10 Jul 2026 | Missing Authorization to Authenticated (Subscriber+) Cron Modification via nftb_cron_action_set AJAX Action | 4.3 | <= 3.5.1 | 3.5.2 | Before disclosure |
| 20 Apr 2026 | Unauthenticated Stored Cross-Site Scripting | 7.2 | <= 3.5 | 3.5.1 | Before disclosure |
| 29 Nov 2025 | Missing Authorization | 4.3 | <= 3.5.1 | 3.5.2 | 159 |
| 5 Sep 2025 | Cross-Site Request Forgery | 4.3 | <= 3.5.1 | 3.5.2 | 244 |
| 9 Oct 2024 | Missing Authorization to Authenticated (Subscriber+) Send Telegram Test Message | 4.3 | <= 3.3.1 | 3.3.2 | Same day |
Changelog mentions of security fixes: 3.5.3 (security, XSS).
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Reputation
Last 90 days: no reviews. Lifetime: 4.9.
| Last 90 days | No reviews |
|---|---|
| Lifetime | 4.9 |
| 5 star | 68 |
|---|---|
| 4 star | 2 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 1 |
Momentum
- Active installs
- 4,000+
- Downloads, last full week
- 409
| 4 May 2026 | 868 |
|---|---|
| 11 May 2026 | 398 |
| 18 May 2026 | 357 |
| 25 May 2026 | 278 |
| 1 Jun 2026 | 245 |
| 8 Jun 2026 | 204 |
| 15 Jun 2026 | 237 |
| 22 Jun 2026 | 164 |
| 29 Jun 2026 | 233 |
| 6 Jul 2026 | 214 |
| 13 Jul 2026 | 194 |
| 20 Jul 2026 | 197 |
| 27 Jul 2026 | 283 |
| 3 Aug 2026 | 311 |
| 10 Aug 2026 | 252 |
| 17 Aug 2026 | 273 |
| 24 Aug 2026 | 297 |
| 31 Aug 2026 | 249 |
| 7 Sep 2026 | 347 |
| 14 Sep 2026 | 1,588 |
| 21 Sep 2026 | 792 |
| 28 Sep 2026 | 685 |
| 5 Oct 2026 | 397 |
| 12 Oct 2026 | 383 |
| 19 Oct 2026 | 449 |
| 26 Oct 2026 | 409 |
Weekly downloads over the last 4 weeks are 3% above the 26-week average.
Healthier alternatives
Same job, rated Healthy, higher Canary Score. Never sponsored.
Facts
- Version
- 3.5.5
- Author
- rainafarai
- Added
- 17 Sep 2020
- Last updated
- 18 Sep 2026
- Active installs
- 4,000+
- Requires WordPress
- 4.0
- Tested up to
- 7.1.4
- Requires PHP
- 7.4
- Category
- Communication & Messaging > Transactional Email
- Tags
- AI, mcp, telegram, woocommerce, notification
Other plugins by this author: Partita IVA e Codice Fiscale, Raina Image Compression, Post View Count Editor, Dynamic Post title for CF7
Questions about Notification for Telegram
Is Notification for Telegram still maintained?
Yes. Last release 18 Sep 2026, 18 releases in the last 24 months.
Who owns Notification for Telegram, and has it changed hands?
No change recorded. Main committer rainafarai since Sep 2020.
Was Notification for Telegram removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is Notification for Telegram safe?
6 known vulnerabilities, all fixed (latest in 3.5.3). Not on the exploited list.
Is the latest Notification for Telegram update safe to install?
No ownership change before 3.5.5. No one-star spike after it.