{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-9821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9821 is a high-severity vulnerability in guruteam Bot for Telegram on WooCommerce, published on 12 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9821 and fix it if it is affected.\n\nWhat it is: CVE-2024-9821 is a high-severity vulnerability in guruteam Bot for Telegram on WooCommerce, published on 12 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-9821 in the wild and no public exploit code.\n\nAffected product: guruteam Bot for Telegram on WooCommerce. 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-9821/ (Markdown: https://insights.sbomify.com/CVE-2024-9821/index.md)","id":"CVE-2024-9821","markdown":"https://insights.sbomify.com/CVE-2024-9821/index.md","name":"CVE-2024-9821","record":{"aliases":["GHSA-cfvh-mr6h-3g8q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can disclose Telegram Bot tokens, enabling account takeover via the Login with Telegram feature.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the 'stm_wpcfto_get_settings' AJAX action in all versions up to, and including, 1.2.7.  This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-10-11","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-10-11T15:35:39Z","kind":"github_poc","ref":"https://github.com/RandomRobbieBF/CVE-2024-9821","stars":1,"title":"Bot for Telegram on WooCommerce \u003c= 1.2.4 - Authenticated (Subscriber+) Telegram Bot Token Disclosure to Authentication Bypass"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in Bot for Telegram on WooCommerce","id":"CVE-2024-9821","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":"Pedalo Connector \u003c= 2.0.5 - Authentication Bypass to Administrator","id":"CVE-2024-9822"},"packages":[],"prev":{"headline":"WP 2FA with Telegram \u003c= 3.0 - Two-Factor Authentication Bypass","id":"CVE-2024-9820"},"products":["Bot for Telegram on WooCommerce"],"published":"2024-10-12","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["guruteam"]},"summary":"Authenticated subscribers can disclose Telegram Bot tokens, enabling account takeover via the Login with Telegram feature.","url":"https://insights.sbomify.com/CVE-2024-9821/"}