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.
Published: 2026-07-09
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The LoginPress Pro plugin for WordPress contains a flaw in its Spotify Social Login addon that accepts the unverified "email" field returned by Spotify's /v1/me endpoint. The plugin uses this email directly with get_user_by('email', $profile['email']) to identify and log in an existing WordPress account, without confirming that the Spotify account actually owns the email address. Because the email can be fabricated by creating a Spotify account with any target e‑mail address, an unauthenticated attacker can impersonate any site user, including administrators, thereby achieving full account compromise. This vulnerability maps to CWE‑287, Authentication Bypass.

Affected Systems

The vulnerability affects WordPress sites that use any release of LoginPress Pro up to and including 6.2.3, provided the Spotify Social Login addon is enabled. Sites that rely on this plugin for user authentication are at risk whenever the addon is active.

Risk and Exploitability

The CVSS score of 8.1 indicates high severity, and the EPSS score of <1% reflects a very low probability of current exploitation. The attack requires only the ability to initiate a login request to the WordPress site using the Spotify provider; no further privileges or server‑side access are necessary. Based on the description, the likely attack vector is a server‑side OAuth callback. The exploitation path does not require client‑side interaction. The vulnerability is not listed in the CISA KEV catalog.

Generated by OpenCVE AI on July 29, 2026 at 11:38 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade LoginPress Pro to a version newer than 6.2.3, where the Spotify email verification flaw has been fixed.
  • Disable or uninstall the Spotify Social Login addon until a secure version is released.
  • Implement a verification step that confirms ownership of the email address before allowing OAuth login, or enforce an additional authentication factor for privileged accounts.

Generated by OpenCVE AI on July 29, 2026 at 11:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 10 Jul 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 10 Jul 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Loginpress
Loginpress loginpress Pro
Wordpress
Wordpress wordpress
Vendors & Products Loginpress
Loginpress loginpress Pro
Wordpress
Wordpress wordpress

Thu, 09 Jul 2026 23:45:00 +0000

Type Values Removed Values Added
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.
Title LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email in Spotify OAuth Callback
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Loginpress Loginpress Pro
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-07-10T18:04:50.339Z

Reserved: 2026-06-18T10:27:55.243Z

Link: CVE-2026-12598

cve-icon Vulnrichment

Updated: 2026-07-10T18:04:46.290Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-29T11:45:03Z

Weaknesses