Information disclosure in Guru Team Bot for Telegram on WooCommerce
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.
Summary
The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'stm_wpcfto_get_settings' AJAX action in all versions up to, and including, 1.2.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2024-9821
- 2026-10-03 Alias added: GHSA-cfvh-mr6h-3g8q
References
More Guru Team vulnerabilities
- TI-2026-82280 Authentication bypass in Bot for Telegram on WooCommerce CVSS 3.1CRITICAL 9.8
- TI-2025-22219 WordPress Site Chat on Telegram plugin <= 1.0.4 - PHP Object Injection Vulnerability CVSS 3.1CRITICAL 9.8
- TI-2025-30594 WordPress Bot for Telegram on WooCommerce plugin <= 1.2.6 - Broken Access Control Vulnerability CVSS 3.1MEDIUM 4.3
Sources
- CVE-2024-9821 · CVE Program
- CVE-2024-9821 · NVD
- FIRST EPSS
- GHSA-cfvh-mr6h-3g8q · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences