LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback
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.
Quick answer
LoginPress Pro should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-6.2.3
Fixed versions
- 6.2.4
How to fix it
LoginPress Pro is affected by CVE-2026-12595, a authentication bypass issue in versions up to 6.2.3. Wordfence lists the official remediation as updating to version 6.2.4, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, reservation or booking workflows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has LoginPress Pro installed, including production, staging, multisite, client, WooCommerce, marketplace, and booking environments.
- Confirm the installed LoginPress Pro version and compare it with the affected range from the Wordfence advisory.
- Update LoginPress Pro to version 6.2.4, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable LoginPress Pro or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, marketplace vendor actions, and admin actions for unauthorized activity.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running LoginPress Pro version is version 6.2.4 or newer, and record the patched version in the remediation ticket.
- Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, vendor, payment, booking, invoice, or settings change.
- Review web server, WordPress, security plugin, WAF, database, WooCommerce, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, vendor, editor, administrator, checkout, form, API, booking, reservation, invoice, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-12595?
LoginPress Pro versions listed as affected should be reviewed: *-6.2.3.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.