CVE-2026-12597

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Wordfence) lists LoginPress Pro versions up to and including 6.2.3 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jul 9, 2026
No fix on record yet.
Web page

LoginPress - Best WordPress Custom Login Page Plugin

https://loginpress.pro/

Vendor 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 12× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  3. 2026-10-12 16:36 UTCEG score recompute
  4. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  5. 2026-10-11 20:12 UTCEG score recompute
  6. 2026-10-11 18:24 UTCEG score recompute
  7. 2026-10-11 14:57 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-01 16:00 UTCEG score recompute
  19. 2026-10-01 16:00 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-09-28 09:56 UTCEG score recompute
  24. 2026-09-28 09:55 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 44th percentile
Show 75 more
  1. 2026-09-24 11:22 UTCEG score recompute
  2. 2026-09-24 11:21 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-09-23 05:50 UTCEG score recompute
  5. 2026-09-23 05:50 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  7. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  8. 2026-09-18 05:26 UTCEG score recompute
  9. 2026-09-18 05:26 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-09-13 23:45 UTCEG score recompute
  12. 2026-09-13 23:45 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-09-13 08:16 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-09-12 16:13 UTCEG score recompute
  16. 2026-09-12 16:13 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-09-12 03:18 UTCEG score recompute
  19. 2026-09-12 03:18 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-09-08 03:20 UTCEG score recompute
  25. 2026-09-08 03:20 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  27. 2026-09-06 13:58 UTCEG score recompute
  28. 2026-09-06 13:58 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  30. 2026-09-05 21:59 UTCEG score recompute
  31. 2026-09-05 21:59 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  36. 2026-08-30 19:35 UTCEG score recompute
  37. 2026-08-30 19:35 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  38. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-08-30 06:41 UTCEG score recompute
  40. 2026-08-30 06:41 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  42. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-08-27 21:43 UTCEG score recompute
  44. 2026-08-27 21:43 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  46. 2026-08-27 00:54 UTCEG score recompute
  47. 2026-08-27 00:54 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  48. 2026-08-26 03:46 UTCEG score recompute
  49. 2026-08-26 03:46 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  51. 2026-08-25 11:39 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  52. 2026-08-24 22:44 UTCEG score recompute
  53. 2026-08-24 22:44 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-08-24 09:48 UTCEG score recompute
  55. 2026-08-24 09:48 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  56. 2026-08-23 20:53 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-08-23 07:58 UTCEG score recompute
  58. 2026-08-23 07:58 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-08-22 19:04 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-08-22 06:08 UTCEG score recompute
  62. 2026-08-22 06:07 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-08-21 17:12 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-08-21 04:12 UTCEG score recompute
  66. 2026-08-21 04:12 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  68. 2026-08-20 15:17 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-08-20 02:22 UTCEG score recompute
  70. 2026-08-20 02:22 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  72. 2026-08-19 13:27 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-08-19 00:25 UTCEG score recompute
  74. 2026-08-19 00:25 UTCGHSA enrichmentGHSA-g678-2jj9-7fmj · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12597?
CVE-2026-12597 is a high-severity vulnerability; its CVE record was published on July 9, 2026. 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 loginpressongithublogin() function, which blindly trusts the first element (profile[0]['email']) of the array…
When was the CVE record for CVE-2026-12597 published?
The CVE record for CVE-2026-12597 was published on July 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-12597 actively exploited?
CVE-2026-12597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12597?
CVE-2026-12597 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12597?
No fix for CVE-2026-12597 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists LoginPress Pro versions up to and including 6.2.3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-12597 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12597

Explore →

Is Your Infrastructure Affected by CVE-2026-12597?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs