Notification for Telegram <= 3.3.1 - Missing Authorization to Authenticated (Subscriber+) Send Telegram Test Message
Strategic Overview
- Status
- Patched in 3.3.2
- Affected Plugin
- Notification for Telegram
- Affected Version
<= 3.3.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-9685
At a glance
CVE-2024-9685 is a medium-severity Missing Authorization vulnerability in the Notification for Telegram WordPress plugin, affecting versions <= 3.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.2; sites on affected versions should update now. Disclosed October 2024, reported by István Márton.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Notification for Telegram <= 3.3.1 carries this weakness at nftb_test_action, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Notification for Telegram the fix is 3.3.2: builds <= 3.3.1 are affected, anything from 3.3.2 onward is not.
Remediation
Update to version 3.3.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Notification for Telegram 3.3.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Notification for Telegram
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C