LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback
Strategic Overview
- Status
- Patched in 6.2.4
- Affected Plugin
- LoginPress Pro
- Affected Version
<= 6.2.3- CVSS
- 8.1High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-12595
At a glance
CVE-2026-12595 is a high-severity Improper Authentication vulnerability in the LoginPress Pro WordPress plugin, affecting versions <= 6.2.3. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.2.4; sites on affected versions should update now. Disclosed July 2026, reported by Nguyen Ngoc Duc (duc193).
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
LoginPress Pro <= 6.2.3 carries this weakness at email, and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For LoginPress Pro the fix is 6.2.4: builds <= 6.2.3 are affected, anything from 6.2.4 onward is not.
Remediation
Update to version 6.2.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: LoginPress Pro 6.2.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in LoginPress Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C