Plugins · bot-for-telegram-on-woocommerce · data as of 2026-11-04
Is Bot for Telegram on WooCommerce safe? Known vulnerabilities and latest version
- Status
- Closed 2026-10-23
- Known issues on record
- 3
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate bot-for-telegram-on-woocommerce && wp plugin delete bot-for-telegram-on-woocommerce
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 3 record(s) do not state which versions are affected.
critical 9.8 CVE-2026-109516 · published 2026-10-29
Authentication bypass in Bot for Telegram on WooCommerce (1.3.0 and older)
- Affected
- 1.3.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 1.3.0. The `/wp-json/woo-telegram/v1/main/` REST endpoint is registered with `permission_callback => '__return_true'` and performs no Telegram webhook signature verification, allowing an unauthenticated attacker to POST a forged bot update with a `message.chat.id` set to any WordPress login name; `bftow_get_user_system_id()` resolves this attacker-supplied value to the targeted account via `get_user_by('login', $tgId)` with no ownership proof, and writes a login token computed as `md5($_SERVER['HTTP_USER_AGENT'] . time())` — both inputs are fully attacker-controlled or bounded within seconds using the response's own `Date` header. The resulting token is redeemable at the unauthenticated, capability-check-free, and nonce-less `?action=bftow_create_order&bftow_token=` endpoint, which calls `wp_set_auth_cookie()` unconditionally via `login_user_by_id`, issuing a persistent authenticated session cookie for the targeted account to the attacker. This makes it possible for unauthenticated attackers to log in as any WordPress user, including administrators, given only that user's username.
medium 4.3 CVE-2025-48268 · published 2025-05-19
Missing authorization check in Bot for Telegram on WooCommerce (1.2.6 and older)
- Affected
- 1.2.6 and older
- Fixed in
- 1.2.7
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in Guru Team Bot for Telegram on WooCommerce bot-for-telegram-on-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Bot for Telegram on WooCommerce: from n/a through <= 1.2.6.
high 8.8 CVE-2024-9821 · published 2024-10-12
Missing authorization check in Bot for Telegram on WooCommerce (1.2.7 and older)
- Affected
- 1.2.7 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'stm_wpcfto_get_settings' AJAX action in all versions up to, and including, 1.2.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.
Recent activity
- 2026-10-23 — closed on wordpress.org.
- 2026-10-29 — Authentication bypass disclosed (CVE-2026-109516), fix version not stated.
- 2025-05-19 — Missing authorization check disclosed (CVE-2025-48268), fixed in 1.2.7.
- 2024-10-12 — Missing authorization check disclosed (CVE-2024-9821), fix version not stated.
Get an email when Bot for Telegram on WooCommerce has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Bot for Telegram on WooCommerce (bot-for-telegram-on-woocommerce) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (2) · Authentication bypass (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/bot-for-telegram-on-woocommerce (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/bot-for-telegram-on-woocommerce"><img src="https://laskyr.com/plugins/bot-for-telegram-on-woocommerce/badge.svg" alt="Bot for Telegram on WooCommerce vulnerability status"></a>