LoginPress Pro <= 6.2.3 — Unauthenticated Authentication Bypass via Unverified OAuth Email via GitHub OAuth Callback
CVE-2026-12597Published · Updated Action summary
Affected: ≤6.2.3Update to 6.2.4 or newer
All remediation steps- Severity
- High8.1
- CVSS
- 8.1CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:HAttack complexity- High
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
LoginPress Pro loginpress-pro
- Affected≤ 6.2.3
- Patched in6.2.4
Update to 6.2.4 or newer.
You are affected if you run ≤ 6.2.3. Version 6.2.4 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under LoginPress Pro.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 6.2.4, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch LoginPress Pro to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Nguyen Ngoc Duc (duc193).
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in LoginPress Pro
All 7| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback ≤6.2.3Update to 6.2.4 | CVE-2026-12595 | |
| High8.1 | Unauthenticated Authentication Bypass via Unverified OAuth Email in Spotify OAuth Callback ≤6.2.3Update to 6.2.4 | CVE-2026-12598 | |
| Critical9.8 | Unauthenticated Privilege Escalation ≤6.2.2Update to 6.2.3 | CVE-2026-49058 | |
| Critical9.8 | Authentication Bypass via WordPress.com OAuth provider ≤5.0.1Update to 5.0.2 | CVE-2025-7444 | |
| Medium5.3 | Captcha Bypass <3.0Update to 3.0 | CVE-2024-32676 |
- High8.1Unauthenticated Authentication Bypass via Unverified OAuth Email via Discord OAuth Callback
≤6.2.3Update to 6.2.4
- High8.1Unauthenticated Authentication Bypass via Unverified OAuth Email in Spotify OAuth Callback
≤6.2.3Update to 6.2.4
- Critical9.8Unauthenticated Privilege Escalation
≤6.2.2Update to 6.2.3
- Critical9.8Authentication Bypass via WordPress.com OAuth provider
≤5.0.1Update to 5.0.2
- Medium5.3Captcha Bypass
<3.0Update to 3.0
Timeline
CVE published
Severity high, CVSS 8.1
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.