{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-10097 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10097 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10097 is a high-severity authentication bypass vulnerability in Softaculous Loginizer, published on 5 Nov 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-10097 and fix it if it is affected.\n\nWhat it is: CVE-2024-10097 is a high-severity authentication bypass vulnerability in Softaculous Loginizer, published on 5 Nov 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-10097 in the wild and no public exploit code.\n\nAffected product: Softaculous Loginizer. 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-10097/ (Markdown: https://insights.sbomify.com/CVE-2024-10097/index.md)","id":"CVE-2024-10097","markdown":"https://insights.sbomify.com/CVE-2024-10097/index.md","name":"CVE-2024-10097","record":{"aliases":["GHSA-hv6r-j3r2-cv8r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress security plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication via OAuth to log in as any existing user, including administrators, if specific email conditions are met.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"loginizer","vendor":"loginizer"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The Loginizer Security and Loginizer plugins for WordPress are vulnerable to authentication bypass in all versions up to, and including, 1.9.2. This is due to insufficient verification on the user being returned by the social login token. 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 email and the user does not have an already-existing account for the service returning the token.","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":"Loginizer Security and Loginizer \u003c= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider","id":"CVE-2024-10097","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":"ApplyOnline – Application Form Builder and Manager \u003c 2.6.3 - Unauthenticated Application File Access","id":"CVE-2024-10098"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-10096"},"products":["Loginizer","Loginizer Security"],"published":"2024-11-05","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-27615","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-12650","kev_date_added":null,"published":"2017-08-07"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-12651","kev_date_added":null,"published":"2017-08-07"},{"cvss_score":7.1,"headline":"WordPress Loginizer Plugin \u003c= 1.7.5 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2022-45084","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":6.1,"headline":"Loginizer 1.7.8 - Reflected XSS","id":"CVE-2023-2296","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11366","kev_date_added":null,"published":"2018-05-22"}],"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":["Softaculous","softaculous"]},"summary":"Unauthenticated attackers can bypass authentication via OAuth to log in as any existing user, including administrators, if specific email conditions are met.","url":"https://insights.sbomify.com/CVE-2024-10097/"}