Notification For Telegram
Approved changes feed: RSS · Atom
cpe:2.3:a:rainafarai:notification_for_telegram:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Rainafarai (5ebc7b32-b0c8-54a3-b157-1e359c30e6e7) |
|---|---|
| Product | Notification For Telegram (2eb8bc41-1736-5175-8290-b222c52bcf10) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-7620 |
vulnerable | 2026-07-29 01:09:05.056697 |
Notification for Telegram <= 3.5.1 - Missing Authorization to Authenticated (Subscriber+) Cron Modification via nftb_cron_action_set AJAX Action
MEDIUM (4.3)
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.
Published: 2026-07-11T03:44:20.239Z
Updated: 2026-07-13T14:39:54.504Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40732 |
vulnerable | 2026-07-29 00:49:30.383158 |
WordPress Notification for Telegram plugin <= 3.5 - Cross Site Scripting (XSS) vulnerability
HIGH (7.1)
Unauthenticated Cross Site Scripting (XSS) in Notification for Telegram <= 3.5 versions.
Published: 2026-06-15T20:18:11.884Z
Updated: 2026-06-16T13:35:37.184Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-62993 |
vulnerable | 2026-06-08 07:39:17.135767 |
WordPress Notification for Telegram plugin <= 3.5.1 - Broken Access Control vulnerability
MEDIUM (4.3)
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.
Published: 2025-12-09T14:52:25.243Z
Updated: 2026-04-28T16:14:08.089Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58794 |
vulnerable | 2026-06-08 07:35:19.552090 |
WordPress Notification for Telegram plugin <= 3.5 - Cross Site Request Forgery (CSRF) vulnerability
MEDIUM (4.3)
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.
Published: 2025-09-05T13:45:03.746Z
Updated: 2026-05-12T00:46:36.044Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9685 |
vulnerable | 2026-06-08 07:00:28.534427 |
Notification for Telegram <= 3.3.1 - Missing Authorization to Authenticated (Subscriber+) Send Telegram Test Message
MEDIUM (4.3)
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.
Published: 2024-10-10T02:06:10.487Z
Updated: 2026-04-08T17:14:41.711Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.