Read the docs
TI-2026-10801 Aliases CVE-2026-12597GHSA-g678-2jj9-7fmj

LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via GitHub OAuth Callback

Priority LOW 38CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00568 47th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
LoginPressLoginPress Proup to 6.2.3—No fix listedCNA
  • LoginPress Pro VendorLoginPress Affected up to 6.2.3 Fixed in — No fix listed CNA

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-12597
  2. 2026-10-03 Alias added: GHSA-g678-2jj9-7fmj

References

  • TI-2025-06784 LoginPress Pro <= 5.0.1 - Authentication Bypass via WordPress.com OAuth provider CVSS 3.1CRITICAL 9.8
  • TI-2026-36284 WordPress LoginPress Pro plugin <= 6.2.2 - Privilege Escalation vulnerability CVSS 3.1CRITICAL 9.8
  • TI-2026-10802 LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email in Spotify OAuth Callback CVSS 3.1HIGH 8.1
  • TI-2026-10800 LoginPress Pro <= 6.2.3 - Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback CVSS 3.1HIGH 8.1
  • TI-2024-21557 WordPress LoginPress Pro plugin < 3.0.0 - Unauth. License Activation/Deactivation vulnerability CVSS 3.1MEDIUM 6.5
  • TI-2024-21556 WordPress LoginPress Pro plugin < 3.0.0 - Captcha Bypass vulnerability CVSS 3.1MEDIUM 5.3

Sources