# CVE-2026-109516: The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cw4f-j2mf-3wm9

## What is CVE-2026-109516?

CVE-2026-109516 is a critical vulnerability in guruteam Bot for Telegram on WooCommerce, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-109516?


## How do I fix CVE-2026-109516?

No fix has been published for CVE-2026-109516 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109516 being exploited?

There is no known exploitation of CVE-2026-109516 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109516 and fix it if it is affected.

What it is: CVE-2026-109516 is a critical vulnerability in guruteam Bot for Telegram on WooCommerce, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-109516 in the wild and no public exploit code.

Affected product: guruteam Bot for Telegram on WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109516/ (Markdown: https://insights.sbomify.com/CVE-2026-109516/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109516
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109516
- OSV: https://osv.dev/vulnerability/CVE-2026-109516

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109516/
Summaries are generated and may contain mistakes; the official description above is the record.