dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-12595

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 via Unverified OAuth Email in all versions up to and including 6.2.3. The vulnerability exists in the loginpress_on_discord_login() Discord OAuth callback handler, which accepts the email field returned by Discord's /users/@me endpoint without ever checking that the profile's verified flag is true, then directly maps that email to a local WordPress account via get_user_by('email', $profile['email']) and issues an authenticated session cookie via wp_set_auth_cookie(). This makes it possible for unauthenticated attackers to take over any existing WordPress account — including administrator accounts — by registering a Discord account configured with an unverified email address that matches the target user's registered WordPress email and completing the standard Discord OAuth flow.

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 Discord OAuth callback handler accepts email addresses from Discord without verifying the 'verified' flag, then directly maps the unverified email to a local WordPress account and issues an authenticated session cookie. This allows attackers to hijack any WordPress account by registering a Discord account with an unverified email matching the target user's email address.

MitigationImmediately disable Discord OAuth login in LoginPress Pro until a patched version is available; audit all accounts that used Discord login for signs of compromise and consider requiring password reset for affected users.

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. Confirm LoginPress Pro plugin is installed
    Check WordPress plugins directory for LoginPress Pro, or review the plugin files in wp-content/plugins/ for loginpress-pro folder
    Affected if LoginPress Pro is not installed - not affected
  2. Identify installed LoginPress Pro version
    Check plugin version in loginpress-pro/readme.txt or in WordPress admin under Plugins > Installed Plugins
    Affected if Running any version of LoginPress Pro where Discord OAuth is enabled; version comparison needed against fixed release when available
  3. Verify Discord OAuth login is enabled
    Navigate to LoginPress Pro settings in WordPress admin; look for Discord integration settings under LoginPress > Settings > Social Login section
    Affected if Discord OAuth is enabled in the plugin settings - potentially affected
  4. Check for Discord-based user accounts
    Query WordPress database: SELECT * FROM wp_users u JOIN wp_usermeta m ON u.ID = m.user_id WHERE m.meta_key = 'primary_blog' OR look for user_registered logs matching Discord OAuth registration patterns
    Affected if Users exist who registered via Discord OAuth login - review these accounts for potential compromise
  5. Review login logs for Discord OAuth activity
    Check WordPress access logs or security plugins for POST requests to /wp-login.php?action=discord or OAuth callback URLs containing 'discord'
    Affected if Recent Discord OAuth login activity found - investigate for suspicious account access

User is affected if LoginPress Pro is installed with Discord OAuth login enabled, regardless of version, since the vulnerability allows account hijacking via unverified Discord email mapping

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

Immediately disable Discord OAuth login in LoginPress Pro until a patched version is available; audit all accounts that used Discord login for signs of compromise and consider requiring password reset for affected users.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12595 — 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-12595 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