CVE-2026-7620 json
Notification for Telegram <= 3.5.1 - Missing Authorization to Authenticated (Subscriber+) Cron Modification via nftb_cron_action_set AJAX Action
published 2026-07-11 3 mo ago modified 2026-07-13 3 mo ago also EUVD-2026-43131
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- rainafarai Notification for Telegram
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/01055be6-42ae-405f-9c8b-7acf5297867e?source=cve
- plugins.trac.wordpress.org /browser/notification-for-telegram/trunk/include/nftncron.php#L122
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5.1/include/nftncron.php#L122
- plugins.trac.wordpress.org /browser/notification-for-telegram/trunk/include/nftncron.php#L94
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5.1/include/nftncron.php#L94
- plugins.trac.wordpress.org /browser/notification-for-telegram/trunk/include/nftncron.php#L126
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5.1/include/nftncron.php#L126
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5/include/nftncron.php#L122
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5/include/nftncron.php#L94
- plugins.trac.wordpress.org /browser/notification-for-telegram/tags/3.5/include/nftncron.php#L126
- plugins.trac.wordpress.org /changeset?reponame=&old=3524838%40notification-for-telegram&new=3524838%40notification-for-telegram
Sources
- CVE List CVE-2026-7620
- NVD CVE-2026-7620
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.