CVE-2026-109516
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 47% of all known CVEs.
References
Related Vulnerabilities
Other CWE-287 (Improper Authentication) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-7593 | Critical | 9.8 | 100% | KEV | - |
| CVE-2023-35082 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-35078 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2017-7921 | Critical | 9.8 | 100% | KEV | - |
| CVE-2021-33044 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2023-46805 | High | 8.2 | 100% | KEV + Ransom | - |
Common questions
How do I fix CVE-2026-109516?
No published fix for CVE-2026-109516 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-109516 being actively exploited?
Not that we know of. CVE-2026-109516 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.57% is the estimated probability that it will be exploited in the next 30 days. That is higher than 47% of all scored CVEs.
How severe is CVE-2026-109516?
CVE-2026-109516 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-109516
Markdown
[](https://tridentstack.com/cve/CVE-2026-109516)HTML
<a href="https://tridentstack.com/cve/CVE-2026-109516"><img src="https://tridentstack.com/cve/badge/CVE-2026-109516.svg" alt="CVE-2026-109516"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-29.