{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9627 is a high-severity vulnerability in gsuvorov TeploBot – Telegram Bot for WP, published on 22 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9627 and fix it if it is affected.\n\nWhat it is: CVE-2024-9627 is a high-severity vulnerability in gsuvorov TeploBot – Telegram Bot for WP, published on 22 Oct 2024. 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-2024-9627 in the wild and no public exploit code.\n\nAffected product: gsuvorov TeploBot – Telegram Bot for WP. 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-2024-9627/ (Markdown: https://insights.sbomify.com/CVE-2024-9627/index.md)","id":"CVE-2024-9627","markdown":"https://insights.sbomify.com/CVE-2024-9627/index.md","name":"CVE-2024-9627","record":{"aliases":["GHSA-8jf5-j4v7-7p6r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can view the Telegram Bot Token due to missing authorization checks, allowing them to control the bot.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"teplobot","vendor":"te-st"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The TeploBot - Telegram Bot for WP plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'service_process' function in all versions up to, and including, 1.3. This makes it possible for unauthenticated attackers to view the Telegram Bot Token, which is a secret token to control the bot.","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":"TeploBot - Telegram Bot for WP \u003c= 1.3 - Telegram Bot Token Disclosure","id":"CVE-2024-9627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"WPS Telegram Chat \u003c= 4.6.0 - Authenticated (Subscriber+) Unauthorized Access to Telegram Bot API","id":"CVE-2024-9628"},"packages":[],"prev":{"headline":"Missing authorization in Editorial Assistant by Sovrn","id":"CVE-2024-9626"},"products":["TeploBot – Telegram Bot for WP"],"published":"2024-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["gsuvorov"]},"summary":"Unauthenticated attackers can view the Telegram Bot Token due to missing authorization checks, allowing them to control the bot.","url":"https://insights.sbomify.com/CVE-2024-9627/"}