Description
The LoginPress Pro plugin for WordPress is vulnerable to Authentication Bypass via the GitHub OAuth callback in versions up to, and including, 6.2.3. The vulnerability exists in the loginpress_on_github_login() function, which blindly trusts the first element (profile[0]['email']) of the array returned by GitHub's /user/emails endpoint as an account-binding identifier without verifying that the email carries a verified === true status. This makes it possible for unauthenticated attackers to log in as any existing WordPress user, including administrators, by adding an unverified email address matching a local account to their GitHub profile and triggering the OAuth callback via a crafted code parameter — causing the plugin to call get_user_by('email', ...) and establish an authenticated session for the matched account. Practical exploitation is conditional on GitHub returning the attacker-added unverified email at index 0 of the /user/emails response, as GitHub typically prioritizes the primary verified address first; nonetheless, the absence of any email verification check in the plugin constitutes a fundamental authentication bypass flaw.
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 an authentication bypass flaw that allows an unauthenticated attacker to log in as any existing local user, including administrators. The vulnerability resides in the GitHub OAuth callback handling, where the plugin unconditionally trusts the first e‑mail address returned by GitHub’s /user/emails endpoint as a binding identifier without verifying that the address is marked as verified. By adding an unverified e‑mail that matches a local account in a malicious GitHub profile and triggering the OAuth flow with a crafted code parameter, the plugin retrieves the user by e‑mail and establishes an authenticated session for the matched account.

Affected Systems

LoginPress Pro for WordPress versions 6.2.3 and earlier are affected. If a WordPress site runs any of these releases, the plugin's GitHub OAuth integration is vulnerable to the bypass described above.

Risk and Exploitability

The flaw carries a CVSS score of 8.1, indicating high severity. The EPSS score is less than 1%, suggesting a low likelihood of active exploitation, yet the lack of email verification enables a straightforward remote attack via the OAuth callback. The vulnerability is not listed in the CISA KEV catalog, but it allows remote attackers to gain full access to any Wordpress user account without authentication.

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

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update LoginPress Pro to version 6.2.4 or newer when available.
  • If an immediate upgrade is not possible, disable the GitHub OAuth module or remove any configured GitHub OAuth applications until a patch is applied.
  • Implement an additional check to confirm that the e‑mail returned by GitHub has verified===true before binding it to a local account; for example, add a hook that rejects unverified GitHub e‑mails during the OAuth callback.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 10 Jul 2026 16: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 via the GitHub OAuth callback in versions up to, and including, 6.2.3. The vulnerability exists in the loginpress_on_github_login() function, which blindly trusts the first element (profile[0]['email']) of the array returned by GitHub's /user/emails endpoint as an account-binding identifier without verifying that the email carries a verified === true status. This makes it possible for unauthenticated attackers to log in as any existing WordPress user, including administrators, by adding an unverified email address matching a local account to their GitHub profile and triggering the OAuth callback via a crafted code parameter — causing the plugin to call get_user_by('email', ...) and establish an authenticated session for the matched account. Practical exploitation is conditional on GitHub returning the attacker-added unverified email at index 0 of the /user/emails response, as GitHub typically prioritizes the primary verified address first; nonetheless, the absence of any email verification check in the plugin constitutes a fundamental authentication bypass flaw.
Title LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via GitHub 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-10T15:27:43.854Z

Reserved: 2026-06-18T10:21:22.717Z

Link: CVE-2026-12597

cve-icon Vulnrichment

Updated: 2026-07-10T15:27:40.495Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

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

Weaknesses