{"id":56157,"date":"2025-06-30T23:45:52","date_gmt":"2025-06-30T23:45:52","guid":{"rendered":""},"modified":"2025-08-31T18:38:19","modified_gmt":"2025-09-01T00:38:19","slug":"cve-2025-52572-critical-vulnerability-in-hikka-telegram-userbot","status":"publish","type":"post","link":"https:\/\/www.ameeba.com\/blog\/cve-2025-52572-critical-vulnerability-in-hikka-telegram-userbot\/","title":{"rendered":"<strong>CVE-2025-52572: Critical Vulnerability in Hikka Telegram Userbot<\/strong>"},"content":{"rendered":"<p><strong>Overview<\/strong><\/p>\n<p>The Common Vulnerabilities and Exposures (CVE) system has identified a severe vulnerability, CVE-2025-52572, affecting all versions of the popular Telegram userbot, Hikka. This vulnerability has the potential to compromise entire systems and leak sensitive data, making it a pressing concern for all Hikka users. With a CVSS severity score of 10.0, the maximum possible, it represents a significant <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-20217-denial-of-service-vulnerability-in-snort-3-detection-engine-of-cisco-secure-firewall-threat-defense-software\/\"  data-wpil-monitor-id=\"77101\">threat to the security<\/a> and privacy of users and their data.<br \/>\nThe <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-50201-critical-os-command-injection-vulnerability-in-wegia-web-manager\/\"  data-wpil-monitor-id=\"62892\">vulnerability lies in the Hikka bot&#8217;s web<\/a> interface and can be exploited in two distinct scenarios. The first scenario occurs when the web interface lacks an authenticated session, allowing an attacker to use their Telegram account to gain <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-49220-pre-authentication-remote-code-execution-in-trend-micro-apex-central\/\"  data-wpil-monitor-id=\"62557\">remote code execution<\/a> (RCE) to the server. The second scenario involves an authenticated session, where a lack of sufficient warning in the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-52921-critical-vulnerability-in-innoshop-allows-code-execution-by-authenticated-attackers\/\"  data-wpil-monitor-id=\"63500\">authentication message tempts users to allow<\/a> potentially damaging actions.<\/p>\n<p><strong>Vulnerability Summary<\/strong><\/p>\n<p>CVE ID: CVE-2025-52572<br \/>\nSeverity: Critical (10.0 CVSS Score)<br \/>\nAttack Vector: Network<br \/>\nPrivileges Required: None<br \/>\nUser Interaction: Required<br \/>\nImpact: <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-5866-critical-vulnerability-in-rt-thread-5-1-0-potentially-leading-to-system-compromise-or-data-leakage\/\"  data-wpil-monitor-id=\"63827\">System compromise and data<\/a> leakage<\/p>\n<p><strong>Affected Products<\/strong><\/p><div id=\"ameeb-1316119065\" class=\"ameeb-content-2 ameeb-entity-placement\"><div style=\"border-left: 4px solid #555; padding-left: 20px; margin: 48px 0; font-family: Roboto, sans-serif; color: #ffffff; line-height: 1.6; max-width: 700px;\">\r\n  <h2 style=\"margin-top: 0; font-size: 20px; font-weight: 600; display: flex; align-items: center;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"display: inline-flex; align-items: center; margin-right: 8px;\">\r\n      <img decoding=\"async\" src=\"https:\/\/www.ameeba.com\/blog\/wp-content\/uploads\/2025\/10\/Best-App-icon-Ameeba.png\" alt=\"Ameeba Chat Icon\" style=\"width: 40px; height: 40px;\" \/>\r\n    <\/a>\r\n    A new way to communicate\r\n  <\/h2>\r\n\r\n  <p style=\"margin-bottom: 12px;\">\r\n    Ameeba Chat is built on encrypted identity, not personal profiles.\r\n  <\/p>\r\n\r\n  <p style=\"margin-bottom: 16px;\">\r\n    Message, call, share files, and coordinate with identities kept separate.\r\n  <\/p>\r\n\r\n  <ul style=\"list-style: none; padding-left: 0; margin-bottom: 20px;\">\r\n    <li>\u2022 Encrypted identity<\/li>\r\n    <li>\u2022 Ameeba Chat authenticates access<\/li>\r\n    <li>\u2022 Aliases and categories<\/li>\r\n    <li>\u2022 End-to-end encrypted chat, calls, and files<\/li>\r\n    <li>\u2022 Secure notes for sensitive information<\/li>\r\n  <\/ul>\r\n\r\n  <p style=\"font-style: italic; font-weight: 600; margin-bottom: 24px;\">\r\n    Private communication, rethought.\r\n  <\/p>\r\n\r\n  <div style=\"display: flex; flex-wrap: wrap; gap: 12px;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\/download\" style=\"background-color: #ffffff; color: #000000; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Download Ameeba Chat<\/a>\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"border: 1px solid #ffffff; color: #ffffff; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Learn More<\/a>\r\n  <\/div>\r\n<\/div>\r\n<\/div>\n<p>Product | Affected Versions<\/p>\n<p>Hikka (Telegram Userbot) | All Versions<\/p>\n<p><strong>How the Exploit Works<\/strong><\/p>\n<p>The exploit takes advantage of flaws in Hikka&#8217;s web interface. In the first scenario, if the interface lacks an authenticated session, an attacker can use their <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-49151-unauthenticated-attackers-can-forge-json-web-tokens-in-microsens-nmp-web\/\"  data-wpil-monitor-id=\"64554\">Telegram<\/a> account to authorize in the dangling web interface and gain RCE to the server. In the second scenario, with an authenticated session, an attacker can manipulate <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2023-47294-critical-vulnerability-in-ncr-terminal-handler-v1-5-1-allows-user-account-manipulation\/\"  data-wpil-monitor-id=\"63749\">users into allowing<\/a> potentially harmful actions due to insufficient warning in the authentication message. This not only enables RCE but also grants the attacker access to the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-34509-hardcoded-user-account-in-sitecore-xm-and-xp-enabling-unauthenticated-remote-access\/\"  data-wpil-monitor-id=\"62776\">Telegram<\/a> accounts of the owners.<\/p>\n<p><strong>Conceptual Example Code<\/strong><\/p><div id=\"ameeb-1912507845\" class=\"ameeb-content ameeb-entity-placement\"><div class=\"poptin-embedded\" data-id=\"f6b387694f681\"><\/div>\r\n\r\n\r\n\r\n\r\n\r\n<\/div>\n<p>Given the nature of this vulnerability, a conceptual example would involve an attacker using their own Telegram account to authorize in the dangling web interface of an unsecured Hikka userbot. This could potentially look something like this:<\/p>\n<pre><code class=\"\" data-line=\"\">import telebot\nbot = telebot.TeleBot(&#039;YOUR_BOT_TOKEN&#039;)\n@bot.message_handler(commands=[&#039;start&#039;])\ndef send_welcome(message):\nbot.reply_to(message, &quot;Hello, I am the attacker&#039;s bot. You just allowed me to execute remote code on your server.&quot;)\nbot.polling()<\/code><\/pre>\n<p>In this conceptual example, the attacker&#8217;s bot sends a welcome message to the user, indicating that the user has unknowingly given the bot permission to <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-49212-trend-micro-endpoint-encryption-policyserver-pre-authentication-remote-code-execution-vulnerability\/\"  data-wpil-monitor-id=\"62585\">execute remote code<\/a>. The actual exploit would be far more complex and malicious, but this <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-50213-special-element-injection-vulnerability-in-apache-airflow-providers-snowflake\/\"  data-wpil-monitor-id=\"64006\">provides a basic idea of how the vulnerability<\/a> could be exploited.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview The Common Vulnerabilities and Exposures (CVE) system has identified a severe vulnerability, CVE-2025-52572, affecting all versions of the popular Telegram userbot, Hikka. This vulnerability has the potential to compromise entire systems and leak sensitive data, making it a pressing concern for all Hikka users. With a CVSS severity score of 10.0, the maximum possible, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[1],"tags":[],"vendor":[],"product":[],"attack_vector":[80],"asset_type":[],"severity":[],"exploit_status":[],"class_list":["post-56157","post","type-post","status-publish","format-standard","hentry","category-uncategorized","attack_vector-rce"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/56157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/comments?post=56157"}],"version-history":[{"count":10,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/56157\/revisions"}],"predecessor-version":[{"id":69477,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/56157\/revisions\/69477"}],"wp:attachment":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/media?parent=56157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/categories?post=56157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/tags?post=56157"},{"taxonomy":"vendor","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/vendor?post=56157"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/product?post=56157"},{"taxonomy":"attack_vector","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/attack_vector?post=56157"},{"taxonomy":"asset_type","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/asset_type?post=56157"},{"taxonomy":"severity","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/severity?post=56157"},{"taxonomy":"exploit_status","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/exploit_status?post=56157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}