CVE-2026-109516 — WordPress is vulnerable to Bot for Telegram on WooCommerce — CWE-287
CVE-2026-109516 is a CRITICAL severity security vulnerability (CWE-287) (CVSS 9.8/10) affecting WordPress is vulnerable to Bot for Telegram on WooCommerce. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-109516
CVSS 9.8/10 · CRITICAL · 29.10.2026
CWE: CWE-287
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Authentication Bypass
Summary: 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 up…
⚡ ATTACK CHAIN
1. JWT: change alg to none, remove signature.
2. SQL bypass: ' OR '1'='1'-- in login form.
3. Direct API endpoint access without auth headers.
4. Password reset token prediction or race condition.
5. Credential stuffing with default creds.
🔧 Tools: jwt_tool, Burp Suite, Hydra, sqlmap --forms
🗺️ MITRE ATT&CK: T1078 (Valid Accounts), T1110 (Brute Force)
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; data can be modified or deleted; service can be completely taken down.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add MFA, strengthen sessions, implement rate limiting.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
🚨 NOW (24-48h) — Remote, no-auth, low complexity.
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query