{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9820 is a medium-severity authentication bypass vulnerability in dueclic AuthPress, published on 15 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-9820 and fix it if it is affected.\n\nWhat it is: CVE-2024-9820 is a medium-severity authentication bypass vulnerability in dueclic AuthPress, published on 15 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-9820 in the wild and no public exploit code.\n\nAffected product: dueclic AuthPress. 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-9820/ (Markdown: https://insights.sbomify.com/CVE-2024-9820/index.md)","id":"CVE-2024-9820","markdown":"https://insights.sbomify.com/CVE-2024-9820/index.md","name":"CVE-2024-9820","record":{"aliases":["GHSA-x23h-whff-jxq7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can bypass two-factor authentication in the WP 2FA with Telegram plugin by exploiting cookie-stored codes, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_2fa_with_telegram","vendor":"dueclic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-565","name":"Reliance on Cookies without Validation and Integrity Checking"},{"id":"CWE-784","name":"Reliance on Cookies without Validation and Integrity Checking in a Security Decision"}],"description":"The WP 2FA with Telegram plugin for WordPress is vulnerable to Two-Factor Authentication Bypass in versions up to, and including, 3.0. This is due to the two-factor code being stored in a cookie, which makes it possible to bypass two-factor authentication.","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":"WP 2FA with Telegram \u003c= 3.0 - Two-Factor Authentication Bypass","id":"CVE-2024-9820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Bot for Telegram on WooCommerce","id":"CVE-2024-9821"},"packages":[],"prev":{"headline":"IDOR in NextGEO's NG Analyser","id":"CVE-2024-9819"},"products":["AuthPress"],"published":"2024-10-15","related":[{"cvss_score":8.8,"headline":"WP 2FA with Telegram \u003c= 3.0 - Authenticated (Subscriber+) Authentication Bypass","id":"CVE-2024-9687","kev_date_added":null,"published":"2024-10-15"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["dueclic"]},"summary":"Attackers can bypass two-factor authentication in the WP 2FA with Telegram plugin by exploiting cookie-stored codes, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2024-9820/"}