Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-109516critical9.8

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

Impact

The Bot for Telegram on WooCommerce plugin for WordPress, versions up to 1.3.0, has an authentication bypass vulnerability. An unauthenticated attacker can exploit this to take over any account. The weakness is due to improper authentication, allowing an attacker to forge a Telegram webhook and brute-force a login token.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

guruteam · Wordfence

Bot for Telegram on WooCommerce

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → through 1.3.0

semver versions

unaffected

unknown

Other versions: unaffected

Original source 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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-109516

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-287 ↗

CWE-287 Improper Authentication

Wordfence

Related →
Contributing organizations · 2
Wordfence

Assigning organization

2026-10-29
CISA-ADP

Additional data publisher

2026-10-29

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

7 sources