Subscriber-level cron manipulation via unchecked AJAX handler
Published Jul 11, 2026 · Updated Jul 11, 2026
Authorization bypass in Notification for Telegram 3.5.1 and earlier allows remote authenticated users to alter a WordPress cron event. The nftb_cron_action_set AJAX handler in include/nftncron.php manages nftb_cron_hook without verifying that the requester has the required capability. Subscriber-level access is sufficient, but the vendor states that the affected file was not loaded by the plugin, so normal plugin execution does not expose the handler.
Summary
What happened
Authorization bypass in Notification for Telegram 3.5.1 and earlier allows remote authenticated users to alter a WordPress cron event. The nftb_cron_action_set AJAX handler in include/nftncron.php manages nftb_cron_hook without verifying that the requester has the required capability. Subscriber-level access is sufficient, but the vendor states that the affected file was not loaded by the plugin, so normal plugin execution does not expose the handler.
The record
- CVE
- CVE-2026-7620
- Published
- Jul 11, 2026
- Updated
- Jul 11, 2026
- Vendor
- rainafarai
- Product
- Notification for Telegram
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 11, 2026CVE publishedPublication date reported by the CVE source.
- Jul 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo