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.
CVE-2026-12597
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EPSS
- 34.1%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 10, 2026
Advisory Details (1)
Auto-updated Jul 9, 2026Vendor Advisories for CVE-2026-12597(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 09:03 UTCEG score recompute
- 2026-07-15 09:03 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 20:07 UTCEG score recompute
- 2026-07-14 20:07 UTCGHSA enrichment
- 2026-07-14 07:08 UTCEG score recompute
- 2026-07-14 07:08 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 18:12 UTCEG score recompute
- 2026-07-13 18:12 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 05:17 UTCEG score recompute
- 2026-07-13 05:17 UTCGHSA enrichment
- 2026-07-12 16:22 UTCEG score recompute
- 2026-07-12 16:22 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:27 UTCEG score recompute
- 2026-07-12 03:27 UTCGHSA enrichment
- 2026-07-11 14:32 UTCEG score recompute
- 2026-07-11 14:32 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 01:35 UTCEG score recompute
- 2026-07-11 01:34 UTCGHSA enrichment
- 2026-07-10 12:39 UTCEG score recompute
- 2026-07-10 12:39 UTCGHSA enrichment
Show 2 moreShow fewer
- 2026-07-09 23:44 UTCEG score recompute
- 2026-07-09 23:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-12597?
When was CVE-2026-12597 disclosed?
Is CVE-2026-12597 actively exploited?
What is the CVSS score of CVE-2026-12597?
How do I remediate CVE-2026-12597?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12597
Is Your Infrastructure Affected by CVE-2026-12597?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.