Contact Form 7 + Telegram <= 0.8.5 - Missing Authorization to Authenticated (Subscriber+) Subscription Approve/Pause/Refuse
Strategic Overview
- Status
- Patched in 0.8.6
- Affected Plugin
- Message Bridge for Contact Form 7 and Telegram
- Affected Version
<= 0.8.5- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-9629
At a glance
CVE-2024-9629 is a medium-severity Missing Authorization vulnerability in the Message Bridge for Contact Form 7 and Telegram WordPress plugin, affecting versions <= 0.8.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.8.6; sites on affected versions should update now. Disclosed October 2024, reported by István Márton.
Vulnerability Overview
The Contact Form 7 + Telegram plugin for WordPress is vulnerable to unauthorized modification of data and loss of data due to a missing capability check on the 'wpcf7_Telegram::ajax' function in versions up to, and including, 0.8.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to approve, pause and refuse subscriptions.
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
Reaching this weakness in Message Bridge for Contact Form 7 and Telegram <= 0.8.5 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 Message Bridge for Contact Form 7 and Telegram the fix is 0.8.6: builds <= 0.8.5 are affected, anything from 0.8.6 onward is not.
Remediation
Update to version 0.8.6, 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: Message Bridge for Contact Form 7 and Telegram 0.8.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C