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-2025-52572: CWE-287: Improper Authentication in hikariatama Hikka

0
Critical
VulnerabilityCVE-2025-52572cvecve-2025-52572cwe-287
Published: Tue Jun 24 2025 (06/24/2025, 20:10:18 UTC)
Source: CVE Database V5
Vendor/Project: hikariatama
Product: Hikka

Description

Hikka, a Telegram userbot, has vulnerability affects all users on all versions of Hikka. Two scenarios are possible. 1. Web interface does not have an authenticated session: attacker can use his own Telegram account to gain RCE to the server by authorizing in the dangling web interface. 2. Web interface does have an authenticated session: due to insufficient warning in the authentication message, users were tempted to click "Allow" in the "Allow web application ops" menu. This gave an attacker access not only to remote code execution, but also to Telegram accounts of owners. Scenario number 2 is known to have been exploited in the wild. No known patches are available, but some workarounds are available. Use `--no-web` flag and do not start userbot without it; after authorizing in the web interface, close the port on the server and/or start the userbot with `--no-web` flag; and do not click "Allow" in your helper bot unless it is your explicit action that needs to be allowed.

AI-Powered Analysis

AILast updated: 12/08/2025, 17:47:12 UTC

Technical Analysis

CVE-2025-52572 is an improper authentication vulnerability (CWE-287) in the Hikka Telegram userbot, affecting all versions up to 1.7.0-wip. The vulnerability arises from the web interface's failure to enforce proper authentication, allowing attackers to leverage two main attack vectors. First, if the web interface is left unauthenticated, an attacker can use their own Telegram account to gain remote code execution (RCE) on the server by authorizing through the exposed interface. Second, even when the web interface is authenticated, insufficient warning messages in the authentication prompt can mislead users into clicking "Allow" in the "Allow web application ops" menu. This user interaction grants attackers not only RCE capabilities but also access to the victim's Telegram accounts. The second scenario has been exploited in the wild, demonstrating the vulnerability's real-world impact. No official patches have been released yet, but recommended workarounds include running the userbot with the --no-web flag to disable the web interface, closing the server port after authorization, and exercising caution by not clicking "Allow" unless explicitly intended. The vulnerability has a CVSS v3.1 score of 10.0, reflecting its critical nature with network attack vector, no required privileges or user interaction, and complete compromise of confidentiality, integrity, and availability. The scope is broad as all Hikka users on affected versions are vulnerable. This vulnerability poses a severe risk to any organization relying on Hikka userbots, especially those exposing the web interface to untrusted networks or lacking strict operational controls.

Potential Impact

For European organizations, this vulnerability presents a critical threat due to the potential for full system compromise via remote code execution and unauthorized access to Telegram accounts. Organizations using Hikka userbots for automation, communication, or integration with Telegram risk exposure of sensitive data, disruption of services, and potential lateral movement within networks. The compromise of Telegram accounts could lead to further social engineering attacks, data leakage, and reputational damage. Given the lack of official patches, organizations face prolonged exposure unless mitigations are applied. The impact is heightened for entities in sectors with high reliance on secure communications such as finance, government, and critical infrastructure. Additionally, the ability for attackers to execute arbitrary code remotely could facilitate deployment of ransomware or other malware, amplifying operational and financial damage. The vulnerability's exploitation could also undermine trust in Telegram-based automation tools, affecting broader digital communication ecosystems in Europe.

Mitigation Recommendations

European organizations should immediately implement the following specific mitigations: 1) Deploy the Hikka userbot with the --no-web flag to disable the vulnerable web interface entirely, preventing unauthorized access. 2) If web interface use is necessary, restrict access via network-level controls such as firewall rules or VPNs to trusted IP addresses only, and close the web interface port immediately after authorization. 3) Educate users and administrators not to click "Allow" on any authentication prompts unless they explicitly initiated the action, reducing the risk of social engineering exploitation. 4) Monitor network traffic and logs for unusual authorization attempts or unexpected web interface activity. 5) Consider isolating userbot servers in segmented network zones to limit potential lateral movement if compromised. 6) Maintain up-to-date backups and incident response plans tailored to potential remote code execution scenarios. 7) Engage with the Hikka community or vendor for updates and patches, and plan for rapid deployment once available. 8) Conduct regular security assessments of Telegram automation tools and their interfaces to identify similar risks proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-06-18T03:55:52.036Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 685b0bc766faf0c1de3b1305

Added to database: 6/24/2025, 8:34:15 PM

Last enriched: 12/8/2025, 5:47:12 PM

Last updated: 1/7/2026, 5:24:09 AM

Views: 154

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats