{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12598 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12598 is a high-severity authentication bypass vulnerability in LoginPress Pro, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12598 and fix it if it is affected.\n\nWhat it is: CVE-2026-12598 is a high-severity authentication bypass vulnerability in LoginPress Pro, published on 9 Jul 2026. 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-2026-12598 in the wild and no public exploit code.\n\nAffected product: LoginPress Pro. 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-2026-12598/ (Markdown: https://insights.sbomify.com/CVE-2026-12598/index.md)","id":"CVE-2026-12598","markdown":"https://insights.sbomify.com/CVE-2026-12598/index.md","name":"CVE-2026-12598","record":{"aliases":["GHSA-cvjp-944x-5rjq"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication and log in as any WordPress user, including administrators, by exploiting unverified email data in the Spotify OAuth callback.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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 LoginPress Pro plugin for WordPress is vulnerable to authentication bypass in versions up to and including 6.2.3 via the Spotify Social Login addon. This is due to the loginpress_on_spotify_login() function trusting the unverified 'email' field returned by Spotify's /v1/me endpoint and using it directly with get_user_by('email', $profile['email']) to identify and log in an existing WordPress account, without confirming that the Spotify user actually owns the email address (Spotify documents that the profile email is unverified) and without requiring the user to prove ownership of the matching WordPress account. This makes it possible for unauthenticated attackers to log in as any existing WordPress user, including Administrators, by registering a Spotify account using the targeted user's email address and authenticating via the Spotify provider.","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":"LoginPress Pro \u003c= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email in Spotify OAuth Callback","id":"CVE-2026-12598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Uncontrolled memory usage in Innodata Labs’ Poppler JPX decoder","id":"CVE-2026-12600"},"packages":[],"prev":{"headline":"LoginPress Pro \u003c= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via GitHub OAuth Callback","id":"CVE-2026-12597"},"products":["LoginPress Pro"],"published":"2026-07-09","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["LoginPress"]},"summary":"Unauthenticated attackers can bypass authentication and log in as any WordPress user, including administrators, by exploiting unverified email data in the Spotify OAuth callback.","url":"https://insights.sbomify.com/CVE-2026-12598/"}