dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-52572

CRITICAL · 10.0 CVSS v3.1 Published 2025-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a critical RCE vulnerability in Hikka Telegram userbot's web interface with two attack vectors. In scenario 1, unauthenticated attackers can gain RCE by authorizing through their own Telegram account on a 'dangling' web interface. In scenario 2 (exploited in the wild), authenticated users are tricked into clicking 'Allow' in a misleading 'Allow web application ops' prompt, granting attackers both RCE and access to the owner's Telegram account.

MitigationUse the --no-web flag to entirely disable the web interface, or immediately close the web port after authentication; never click 'Allow' in the helper bot's web application prompt unless you explicitly initiated that action.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if web interface is enabled
    Run the Hikka process with '--help' and look for the '--no-web' flag documentation, or inspect the process startup command/script to see if '--no-web' is NOT present. Alternatively, check if port 8080 (default web port) is listening.
    Affected if The web interface is enabled (--no-web flag is not used) and port 8080 or similar is open and listening
  2. Identify installed Hikka version
    Run 'pip show hikka' or check the package version in your Python environment. Compare this version number to any officially documented affected versions for CVE-2025-52572.
    Affected if The installed version matches any version range known to contain this vulnerability (no specific range provided in CVE details)
  3. Inspect active web sessions
    Check the web interface's active session list or bot authorized sessions via the Telegram bot interface. Look for unexpected or unknown authorized accounts.
    Affected if There are unexpected or unknown Telegram accounts authorized in the web interface session list
  4. Review helper bot authorizations
    In the Telegram bot interface for Hikka, check the list of authorized helper bots or web application permissions. Look for any suspicious or unrecognized bot authorizations.
    Affected if There are unauthorized or unexpected helper bots with 'Allow web application ops' permissions granted

A user is affected if Hikka's web interface is enabled (no --no-web flag used) AND the installed version is within the vulnerable range, OR if unexpected authorized sessions or helper bot permissions are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Use the --no-web flag to entirely disable the web interface, or immediately close the web port after authentication; never click 'Allow' in the helper bot's web application prompt unless you explicitly initiated that action.

Recommended fix High confidence
  1. Start Hikka with the `--no-web` flag: `python3 -m hikka --no-web` or equivalent command to completely disable the web interface
  2. If you have previously authorized in the web interface, close the port on the server (e.g., firewall rules to block the web interface port) after authorization to prevent dangling sessions
  3. Do not click 'Allow' in the helper bot's 'Allow web application ops' menu unless it is an explicit, intentional action you are performing
  4. Consider running the userbot in an isolated network environment if the web interface must be used temporarily
Caveat Using --no-web flag disables the web interface functionality entirely

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52572 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data