CVE-2026-109516

Bot for Telegram on WooCommerce <= 1.3.0 - Unauthenticated Authentication Bypass to Account Takeover via Fake Telegram Webhook + Brute-Forced Login Token

Published Oct 29, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The Bot for Telegram on WooCommerce plugin allows an attacker to bypass authentication entirely for any WordPress account. By posting a forged webhook to the plugin’s REST endpoint, the attacker supplies an arbitrary user login name, causing the plugin to generate a login token based on the attacker‑controlled input. Because no signature verification or ownership proof is performed, the attacker can redeem this token at an unauthenticated endpoint, causing WordPress to set an authenticated session cookie for the targeted account and enabling full account takeover, including administrative privileges.

Affected Systems

The flaw is present in all releases of the guruTeam Bot for Telegram on WooCommerce WordPress plugin up to version 1.3.0. Any WordPress site that has installed this plugin and is connected to WooCommerce is affected, regardless of theme or other active plugins.

Risk and Exploitability

The CVSS score of 9.8 classifies the vulnerability as critical, and the EPSS score is not available, but the lack of requirement for prior authentication and the simplicity of the exploit make it highly feasible for threat actors. An attacker needs only the target's username, which can be discovered or guessed, to proceed. The public REST endpoint and absence of signature checks mean the attack can be launched remotely without any privileged access. Although the vulnerability is not listed as a known exploited vulnerability, its severity demands swift remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Bot for Telegram on WooCommerce plugin to a version newer than 1.3.0 as soon as one is available; if no update is available, remove the plugin entirely.
  • Block or restrict POST requests to the /wp-json/woo-telegram/v1/main/ endpoint using firewall rules or plugin settings so that only trusted sources can access it.
  • Enforce HTTPS sitewide, enable HTTP Strict Transport Security, and implement an additional webhook signature check or IP whitelist on the server side to guard against future similar bypasses.
  • Immediately change passwords for all WordPress accounts that may have been affected and revoke any related authentication tokens.

Generated by OpenCVE AI on October 29, 2026 at 04:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Guruteam
Guruteam bot For Telegram On Woocommerce
Wordpress-extensions
Wordpress-extensions bot For Telegram On Woocommerce
Vendors & Products Guruteam
Guruteam bot For Telegram On Woocommerce
Wordpress-extensions
Wordpress-extensions bot For Telegram On Woocommerce
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Bot for Telegram on WooCommerce <= 1.3.0 - Unauthenticated Authentication Bypass to Account Takeover via Fake Telegram Webhook + Brute-Forced Login Token
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Oct 29, 2026, 10:45 AM
Reserved
Oct 12, 2026, 6:05 PM
Status
Deferred
Published
Oct 29, 2026, 4:18 AM
Modified
Oct 29, 2026, 2:56 PM