{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-52572 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52572 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-52572 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-52572 in the wild and no public exploit code.\n\nAffected product: hikariatama Hikka. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52572/ (Markdown: https://insights.sbomify.com/CVE-2025-52572/index.md)","id":"CVE-2025-52572","markdown":"https://insights.sbomify.com/CVE-2025-52572/index.md","name":"CVE-2025-52572","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"workaround","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Telegram userbot","requires_auth":"none","summary":"Attackers can achieve remote code execution and account takeover via a dangling web interface or social engineering in Hikka Telegram userbot.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hikka vulnerable to RCE through dangling web interface","id":"CVE-2025-52572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Command Injection in MCP Server ios-simulator-mcp","id":"CVE-2025-52573"},"packages":[],"prev":{"headline":"Hikka vulnerable to RCE through edits in a channel","id":"CVE-2025-52571"},"products":["Hikka"],"published":"2025-06-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-08","vendors":["hikariatama"]},"summary":"Attackers can achieve remote code execution and account takeover via a dangling web interface or social engineering in Hikka Telegram userbot.","url":"https://insights.sbomify.com/CVE-2025-52572/"}