CVE-2026-12597
Auth bypass in LoginPress Pro GitHub OAuth allows account takeover.
Is CVE-2026-12597 being exploited?
Not confirmed. CVE-2026-12597 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-12597?
CVE-2026-12597 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-12597?
Not known from our data. No patch reference has been recorded for CVE-2026-12597, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-12597 affect?
CVE-2026-12597 affects LoginPress Pro WordPress plugin (<=6.2.3), WordPress sites using LoginPress GitHub OAuth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12597?
Disable LoginPress GitHub OAuth or remove plugin; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can log in as any WordPress user, including administrators, by abusing GitHub OAuth email handling.
Immediate action required
- affected<= 6.2.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.