CVE-2025-52572

{"id": "CVE-2025-52572", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 10.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.9}]}, "published": "2025-06-24T21:15:25.463", "references": [{"url": "https://github.com/hikariatama/Hikka/security/advisories/GHSA-7x3c-335v-wxjj", "source": "security-advisories@github.com"}, {"url": "https://t.me/bbcode/9", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Hikka, un bot de usuario de Telegram, presenta una vulnerabilidad que afecta a todos los usuarios en todas las versiones de Hikka. Existen dos escenarios posibles: 1. La interfaz web no tiene una sesi\u00f3n autenticada: el atacante puede usar su propia cuenta de Telegram para acceder al servidor mediante la autorizaci\u00f3n en la interfaz web inactiva. 2. La interfaz web s\u00ed tiene una sesi\u00f3n autenticada: debido a una advertencia insuficiente en el mensaje de autenticaci\u00f3n, los usuarios se vieron tentados a hacer clic en \"Permitir\" en el men\u00fa \"Permitir operaciones de aplicaciones web\". Esto permiti\u00f3 al atacante acceder no solo a la ejecuci\u00f3n remota de c\u00f3digo, sino tambi\u00e9n a las cuentas de Telegram de los propietarios. Se sabe que el escenario n\u00famero 2 ha sido explotado in situ. No existen parches conocidos, pero existen algunas soluciones alternativas. Use el indicador `--no-web` y no inicie el bot de usuario sin \u00e9l; despu\u00e9s de autorizar en la interfaz web, cierre el puerto en el servidor o inicie el bot de usuario con el indicador `--no-web`; y no haga clic en \"Permitir\" en su bot auxiliar a menos que sea su acci\u00f3n expl\u00edcita la que deba permitirse."}], "lastModified": "2025-06-26T18:58:14.280", "sourceIdentifier": "security-advisories@github.com"}