{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9989 exists.","fix":"No fix has been published for CVE-2024-9989 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9989 is a critical authentication bypass vulnerability in odude Crypto Tool, published on 29 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-9989 and fix it if it is affected.\n\nWhat it is: CVE-2024-9989 is a critical authentication bypass vulnerability in odude Crypto Tool, published on 29 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9989 exists.\n\nAffected product: odude Crypto Tool. 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-9989/ (Markdown: https://insights.sbomify.com/CVE-2024-9989/index.md)","id":"CVE-2024-9989","markdown":"https://insights.sbomify.com/CVE-2024-9989/index.md","name":"CVE-2024-9989","record":{"aliases":["GHSA-hmfh-w3mx-w6j4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can log in as any existing user, including administrators, by exploiting an authentication bypass in the Crypto plugin.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"crypto_tool","vendor":"odude"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.18. This is due to a limited arbitrary method call to 'crypto_connect_ajax_process::log_in' function in the 'crypto_connect_ajax_process' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the username.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-9989.yaml","stars":null,"title":"Crypto \u003c= 2.15 - Authentication Bypass"}],"tier":"weaponised"},"has_fix":null,"headline":"Crypto \u003c= 2.18 - Authentication Bypass via log_in","id":"CVE-2024-9989","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Crypto \u003c= 2.15 - Cross-Site Request Forgery to Authentication Bypass","id":"CVE-2024-9990"},"packages":[],"prev":{"headline":"Crypto \u003c= 2.19 - Authentication Bypass via register","id":"CVE-2024-9988"},"products":["Crypto Tool"],"published":"2024-10-29","related":[{"cvss_score":9.8,"headline":"Crypto \u003c= 2.19 - Authentication Bypass via register","id":"CVE-2024-9988","kev_date_added":null,"published":"2024-10-29"},{"cvss_score":8.8,"headline":"Crypto \u003c= 2.15 - Cross-Site Request Forgery to Authentication Bypass","id":"CVE-2024-9990","kev_date_added":null,"published":"2024-10-29"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["odude"]},"summary":"Unauthenticated attackers can log in as any existing user, including administrators, by exploiting an authentication bypass in the Crypto plugin.","url":"https://insights.sbomify.com/CVE-2024-9989/"}