Unauthorized test-message delivery via missing capability check
Published Oct 10, 2024 · Updated Apr 8, 2026
Missing authorization in Notification for Telegram 3.3.1 and earlier allows remote authenticated users to send Telegram test messages. The nftb_test_action AJAX handler accepts a test-message request and invokes the Telegram Bot API without checking the caller's capability. Subscriber-level access is sufficient to trigger delivery to every Telegram recipient configured in the plugin, modifying external message state without broader site control.
Summary
What happened
Missing authorization in Notification for Telegram 3.3.1 and earlier allows remote authenticated users to send Telegram test messages. The nftb_test_action AJAX handler accepts a test-message request and invokes the Telegram Bot API without checking the caller's capability. Subscriber-level access is sufficient to trigger delivery to every Telegram recipient configured in the plugin, modifying external message state without broader site control.
The record
- CVE
- CVE-2024-9685
- Published
- Oct 10, 2024
- Updated
- Apr 8, 2026
- Vendor
- rainafarai
- Product
- Notification for Telegram
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 10, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.3.1
What conditions does exploitation require?
What is affected?
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