Skip to content
Laskyr

CVE-2026-109516: Bot for Telegram on WooCommerce authentication bypass vulnerability

critical 9.8 plugin closed published 2026-10-29

Bot for Telegram on WooCommerce is closed on wordpress.org, so no fix is coming through WordPress updates

Bot for Telegram on WooCommerce 1.3.0 and older is affected by this authentication bypass issue. The plugin was closed on wordpress.org on 2026-10-23, so sites running it will not be offered an update.

Affected versions
1.3.0 and older
Fixed in
unknown
Severity
Critical · CVSS 9.8
Active installs
closed
Type
Authentication bypass

What an attacker needs

CVSS vector (score by Wordfence): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What to do now

  1. Replace Bot for Telegram on WooCommerce. A closed plugin gets no updates through WordPress, so this hole stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deactivating alone leaves its files on the server.
  3. Not sure which version you run? Check your version against every known Bot for Telegram on WooCommerce issue.
  4. If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.

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.

Description from the CVE record, published by Wordfence (the CVE Numbering Authority), via the NVD entry for CVE-2026-109516.

References

Related

Ran an affected version? Check your site for signs of a hack

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Already hacked? Flat $499 cleanup with a 30-day reinfection guarantee.

Where this data comes from

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit