<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Bot for Telegram on WooCommerce (&lt;= 1.3.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/bot-for-telegram-on-woocommerce--1.3.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 29 Oct 2026 05:02:59 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/bot-for-telegram-on-woocommerce--1.3.0/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Bot for Telegram on WooCommerce: Authentication bypass and account takeover (CVE-2026-109516)</title><link>https://feed.craftedsignal.io/briefs/2026-10-woo-telegram-auth-bypass/</link><pubDate>Thu, 29 Oct 2026 05:02:59 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-woo-telegram-auth-bypass/</guid><description>The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to unauthenticated account takeover due to missing permission checks and signature validation in its REST API and authentication endpoints.</description><content:encoded><![CDATA[<p>CVE-2026-109516 affects the 'Bot for Telegram on WooCommerce' plugin for WordPress versions 1.3.0 and earlier. The plugin fails to verify Telegram webhook signatures and incorrectly trusts attacker-supplied input within its REST API and order creation actions, leading to full authentication bypass and privilege escalation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker sends a forged HTTP POST request to the <code>/wp-json/woo-telegram/v1/main/</code> endpoint.</li>
<li>The endpoint, lacking a permission callback, accepts the request.</li>
<li>The attacker provides a <code>message.chat.id</code> field set to the target user's login username.</li>
<li>The <code>bftow_get_user_system_id()</code> function retrieves the victim's user ID via <code>get_user_by('login', $tgId)</code> without proof of identity.</li>
<li>The attacker calculates a session token based on their <code>User-Agent</code> and the current <code>time()</code>.</li>
<li>The attacker invokes the <code>?action=bftow_create_order&amp;bftow_token=</code> endpoint with the crafted token.</li>
<li>The plugin calls <code>wp_set_auth_cookie()</code> using the victim's ID, granting the attacker a persistent authenticated session.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to gain persistent administrative access to the WordPress site, enabling full account takeover.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Disable or uninstall the 'Bot for Telegram on WooCommerce' plugin immediately if not currently using a patched version.</li>
<li>Review web server access logs for anomalous POST requests to <code>/wp-json/woo-telegram/v1/main/</code> and GET/POST requests containing <code>action=bftow_create_order</code>.</li>
<li>Audit WordPress user accounts for suspicious activities or unauthorized password/email changes occurring after the deployment of the vulnerable plugin version.</li>
</ol>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category></item></channel></rss>