dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-12598

HIGH · 8.1 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LoginPress Pro plugin's Spotify Social Login addon trusts the unverified 'email' field from Spotify's /v1/me endpoint and uses it directly with get_user_by('email') to authenticate WordPress users without verifying email ownership. Attackers can register a Spotify account with a target user's email and gain unauthorized access to that WordPress account.

MitigationDisable the Spotify Social Login addon immediately until a patch is available that validates the email is verified by Spotify (checking the 'email_verified' field) or implements additional account ownership verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify LoginPress Pro plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) for loginpress-pro folder, or go to Plugins > Installed Plugins in WP Admin and look for LoginPress Pro
    Affected if LoginPress Pro plugin is found installed on the WordPress site
  2. Confirm Spotify Social Login addon is active
    Check wp-content/plugins for a spotify or social-login addon folder associated with LoginPress, or inspect the site's active plugins list via WP Admin or database
    Affected if Spotify Social Login addon is active or installed alongside LoginPress Pro
  3. Check if social login is enabled in plugin settings
    Navigate to LoginPress Pro settings in WordPress Admin (usually under LoginPress > Settings > Social Login) or inspect the wp_options table for option_name containing 'loginpress_social_login' set to enabled
    Affected if Social login functionality is enabled in the plugin configuration
  4. Inspect the authentication flow for email verification
    Review the addon code in the Spotify login module (typically in the addon PHP file handling Spotify OAuth callback) and look for get_user_by('email', $email) calls where $email comes directly from Spotify API response without verification check
    Affected if The code passes the email from Spotify API directly to get_user_by() without verifying email_verified status from Spotify
  5. Compare your LoginPress Pro version to any official advisories
    Check the main loginpress-pro plugin file header for version number, or view the plugin in WP Admin plugins list
    Affected if Your installed version matches or falls within any affected version range published for this CVE

A site is affected if LoginPress Pro with the Spotify Social Login addon is installed, the addon is active, and social login is enabled, allowing unauthenticated attackers to hijack accounts by registering on Spotify with a target user's email address.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the Spotify Social Login addon immediately until a patch is available that validates the email is verified by Spotify (checking the 'email_verified' field) or implements additional account ownership verification.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12598 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data