Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-38789: Cross-Site Request Forgery (CSRF) in Marco Milesi Telegram Bot & Channel

0
Unknown
VulnerabilityCVE-2024-38789cvecve-2024-38789
Published: Thu Jan 02 2025 (01/02/2025, 12:01:08 UTC)
Source: CVE Database V5
Vendor/Project: Marco Milesi
Product: Telegram Bot & Channel

Description

Cross-Site Request Forgery (CSRF) vulnerability in Marco Milesi Telegram Bot & Channel telegram-bot allows Cross Site Request Forgery.This issue affects Telegram Bot & Channel: from n/a through <= 3.8.2.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 05:21:46 UTC

Technical Analysis

CVE-2024-38789 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the Marco Milesi Telegram Bot & Channel software, affecting all versions up to and including 3.8.2. CSRF vulnerabilities occur when a web application or service fails to properly verify that requests originate from legitimate users, allowing attackers to craft malicious requests that execute actions on behalf of authenticated users without their knowledge. In this case, the Telegram Bot & Channel software does not implement sufficient anti-CSRF protections, such as CSRF tokens or strict origin checks, enabling attackers to exploit this weakness. An attacker can lure a victim who is authenticated with the bot into visiting a specially crafted webpage or clicking a malicious link, which then triggers unauthorized commands or actions within the bot or channel context. This can lead to unauthorized message posting, configuration changes, or other bot operations that the attacker controls indirectly. The vulnerability does not require bypassing authentication since the victim must already be logged in, but it exploits the trust relationship between the user and the bot. No public exploits have been reported yet, and no official patches or mitigation links are provided at this time. The vulnerability was reserved in June 2024 and published in January 2025. The absence of a CVSS score necessitates a severity assessment based on impact and exploitability factors.

Potential Impact

The primary impact of CVE-2024-38789 is the unauthorized execution of commands or actions within the Marco Milesi Telegram Bot & Channel environment by exploiting the victim’s authenticated session. This can compromise the integrity of the bot’s operations, allowing attackers to manipulate messages, alter settings, or perform other privileged actions without user consent. Confidentiality impact is limited since the vulnerability does not directly expose sensitive data, but integrity and availability could be significantly affected if attackers disrupt bot functionality or inject malicious content. Organizations using this bot for critical communication, automation, or customer interaction may face operational disruptions, reputational damage, or indirect security risks if attackers leverage the bot to propagate misinformation or malicious payloads. The ease of exploitation via social engineering and the broad deployment of Telegram bots globally increase the threat surface. Although no known exploits exist currently, the vulnerability presents a clear risk that could be weaponized in targeted or widespread attacks.

Mitigation Recommendations

To mitigate CVE-2024-38789, developers and administrators of the Marco Milesi Telegram Bot & Channel should implement robust anti-CSRF protections, including the use of unique, unpredictable CSRF tokens embedded in all state-changing requests. Additionally, validating the HTTP Referer or Origin headers to ensure requests originate from trusted sources can reduce risk. Updating the bot software to a patched version once available is critical. Until patches are released, administrators should restrict bot access to trusted users and channels, monitor for unusual activity, and educate users about the risks of clicking unsolicited links while authenticated. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts can provide an additional layer of defense. Regular security audits and penetration testing focused on CSRF and related web vulnerabilities will help identify and remediate similar issues proactively.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-06-19T15:07:57.035Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd7465e6bfc5ba1def70ad

Added to database: 4/1/2026, 7:39:17 PM

Last enriched: 4/2/2026, 5:21:46 AM

Last updated: 4/5/2026, 7:40:58 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses