{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-9687 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-9687 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9687 is a high-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-9687 and fix it if it is affected.\n\nWhat it is: CVE-2024-9687 is a high-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-9687 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-9687/ (Markdown: https://insights.sbomify.com/CVE-2024-9687/index.md)","id":"CVE-2024-9687","markdown":"https://insights.sbomify.com/CVE-2024-9687/index.md","name":"CVE-2024-9687","record":{"aliases":["GHSA-rfxp-9x8m-jfw8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can bypass two-factor authentication to log in as any user, including administrators, due to insufficient key validation.","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":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-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The WP 2FA with Telegram plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 3.0. This is due to insufficient validation of the user-controlled key on the 'validate_tg' action. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to log in as any existing user on the site, such as an administrator.","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 - Authenticated (Subscriber+) Authentication Bypass","id":"CVE-2024-9687","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":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-9688"},"packages":[],"prev":{"headline":"Order Notification for Telegram \u003c= 1.0.1 - Missing Authorization to Unauthenticated Send Telegram Test Message","id":"CVE-2024-9686"},"products":["AuthPress"],"published":"2024-10-15","related":[{"cvss_score":6.5,"headline":"WP 2FA with Telegram \u003c= 3.0 - Two-Factor Authentication Bypass","id":"CVE-2024-9820","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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["dueclic"]},"summary":"Authenticated subscribers can bypass two-factor authentication to log in as any user, including administrators, due to insufficient key validation.","url":"https://insights.sbomify.com/CVE-2024-9687/"}