CVE-2026-109516: Bot for Telegram on WooCommerce authentication bypass vulnerability
critical 9.8 plugin closed published 2026-10-29
- 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
- Access: None. No account or login is needed.
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
- Replace Bot for Telegram on WooCommerce. A closed plugin gets no updates through WordPress, so this hole stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deactivating alone leaves its files on the server.
- Not sure which version you run? Check your version against every known Bot for Telegram on WooCommerce issue.
- 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.
References
- NVD CVE-2026-109516 nvd.nist.gov
- Wordfence advisory www.wordfence.com
- Plugin source plugins.trac.wordpress.org
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
- CVE record, score and references: 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.
- Versions and install counts: wordpress.org/plugins/bot-for-telegram-on-woocommerce (Plugins API), fetched 2026-11-04.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.