# CVE-2025-52572: Hikka vulnerable to RCE through dangling web interface

> Attackers can achieve remote code execution and account takeover via a dangling web interface or social engineering in Hikka Telegram userbot.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 8 Dec 2025

## What is CVE-2025-52572?

CVE-2025-52572 is a critical authentication bypass vulnerability in hikariatama Hikka, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-52572?


## How do I fix CVE-2025-52572?

No fix has been published for CVE-2025-52572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52572 being exploited?

There is no known exploitation of CVE-2025-52572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52572 and fix it if it is affected.

What it is: CVE-2025-52572 is a critical authentication bypass vulnerability in hikariatama Hikka, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52572 in the wild and no public exploit code.

Affected product: hikariatama Hikka. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52572/ (Markdown: https://insights.sbomify.com/CVE-2025-52572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52572
- OSV: https://osv.dev/vulnerability/CVE-2025-52572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52572/
Summaries are generated and may contain mistakes; the official description above is the record.