Vulnerability · Published Jun 24, 2025 · Assigned by GitHub_M
CVE-2025-52572Hikka vulnerable to RCE through dangling web interface
Critical 10.0
In plain English
A critical-severity improper authentication in Hikka from hikariatama. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.7% (higher than 54% of all known vulnerabilities).
Official 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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| hikariatama | Hikka | <= 1.7.0-wip |
Weakness: CWE-287 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
References
- https://github.com/hikariatama/Hikka/security/advisories/GHSA-7x3c-335v-wxjj x_refsource_CONFIRM
- https://t.me/bbcode/9 x_refsource_MISC