CVE-2026-14262

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-11. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
8.8EG
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.7%CVSS: 8.8Exploit: 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 nicu_m Simple JWT Login – Allows you to use JWT on REST endpoints. versions up to and including 3.6.6 as affected. No release containing a fix is confirmed on record.

The Simple JWT Login – Allows you to use JWT on REST endpoints. plugin for WordPress is vulnerable to Authentication Bypass to Privilege Escalation in all versions up to, and including, 3.6.6 via the payload parameter. The vulnerability exists because AuthenticateService::generatePayload() only overwrites JWT payload keys whose names appear in the admin-configured jwt_payload list — leaving any attacker-supplied identity claims such as email, id, or username intact and signed into the JWT with the site's HS256 secret. This makes it possible for authenticated attackers, with subscriber-level access and above, to escalate their privileges to that of an Administrator by injecting a target administrator's email address into the payload parameter at the /wp-json/simple-jwt-login/v1/auth endpoint, then redeeming the resulting JWT at the /autologin endpoint to obtain a fully authenticated session as that administrator.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.7% × 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.7%
EPSS %ILE
53rd
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 11, 2026

Last Modified

July 13, 2026

References (6)

Vendor Advisories for CVE-2026-14262(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 11× in last 7d / 34× 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-16 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-12 16:34 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-11 20:11 UTCEG score recompute
  8. 2026-10-11 18:23 UTCEG score recompute
  9. 2026-10-11 14:56 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-01 14:54 UTCEG score recompute
  20. 2026-10-01 14:54 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-09-28 09:42 UTCEG score recompute
  25. 2026-09-28 09:42 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
Show 75 more
  1. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-09-24 10:29 UTCEG score recompute
  4. 2026-09-24 10:29 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-09-23 05:40 UTCEG score recompute
  6. 2026-09-23 05:40 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-09-18 05:12 UTCEG score recompute
  9. 2026-09-18 05:12 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-09-13 23:37 UTCEG score recompute
  13. 2026-09-13 23:37 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-09-13 08:08 UTCEG score recompute
  16. 2026-09-13 08:08 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-09-12 14:53 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-09-12 02:21 UTCEG score recompute
  20. 2026-09-12 02:21 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-09-08 02:26 UTCEG score recompute
  26. 2026-09-08 02:26 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  28. 2026-09-06 13:54 UTCEG score recompute
  29. 2026-09-06 13:54 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  31. 2026-09-05 21:36 UTCEG score recompute
  32. 2026-09-05 21:36 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  34. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  35. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  38. 2026-08-30 18:29 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-08-30 05:57 UTCEG score recompute
  40. 2026-08-30 05:57 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  41. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-08-27 21:38 UTCEG score recompute
  44. 2026-08-27 21:38 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  45. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  46. 2026-08-27 00:32 UTCEG score recompute
  47. 2026-08-27 00:32 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-08-26 02:47 UTCEG score recompute
  49. 2026-08-26 02:46 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-08-25 10:29 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  52. 2026-08-24 21:55 UTCEG score recompute
  53. 2026-08-24 21:55 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-08-24 09:23 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  55. 2026-08-23 18:52 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-08-23 06:19 UTCEG score recompute
  57. 2026-08-23 06:19 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  59. 2026-08-22 17:47 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-08-22 05:14 UTCEG score recompute
  61. 2026-08-22 05:14 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  62. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-08-21 16:41 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  64. 2026-08-21 03:43 UTCEG score recompute
  65. 2026-08-21 03:43 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  67. 2026-08-20 14:46 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-08-20 01:28 UTCEG score recompute
  69. 2026-08-20 01:28 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  70. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  71. 2026-08-19 09:15 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-08-18 20:31 UTCEG score recompute
  73. 2026-08-18 20:31 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8
  74. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  75. 2026-08-18 04:42 UTCGHSA enrichmentGHSA-4f4m-2qm7-575f · GitHub severity HIGH · GitHub CVSS 8.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14262?
CVE-2026-14262 is a high-severity vulnerability; its CVE record was published on July 11, 2026. The Simple JWT Login – Allows you to use JWT on REST endpoints. plugin for WordPress is vulnerable to Authentication Bypass to Privilege Escalation in all versions up to, and including, 3.6.6 via the payload parameter. The vulnerability exists because AuthenticateService::generatePayload() only…
When was the CVE record for CVE-2026-14262 published?
The CVE record for CVE-2026-14262 was published on July 11, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-14262 actively exploited?
CVE-2026-14262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14262?
CVE-2026-14262 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14262?
No fix for CVE-2026-14262 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 nicu_m Simple JWT Login – Allows you to use JWT on REST endpoints. versions up to and including 3.6.6 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-14262 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14262?

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

Book a Demo →Browse All CVEs