CVE-2026-14495

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%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 DoLogin Security plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Randomness in all versions up to, and including, 4.3. The vulnerability exists because dologin\s::rrand() seeds the Mersenne Twister with mt_srand((double) microtime() * 1000000) — discarding the integer-seconds component of microtime() and constraining the seed to a range of approximately 10^6 values (~20 bits of entropy) — after which every character of the 32-character magic-link token is drawn sequentially with mt_rand(), making the entire token a deterministic function of that seed. Because Pswdless::try_login() is registered on the unauthenticated init hook, resolves the target account by the auto-increment numeric ID embedded in the ?dologin=. parameter, performs the hash comparison using a non-constant-time != operator, and then calls wp_set_auth_cookie() directly — never passing through wp_authenticate() and therefore never triggering the plugin's own Auth::_has_login_err() lockout — an unauthenticated attacker can brute-force the ~10^6-candidate seed space to reconstruct an active passwordless login token and authenticate as any targeted user, including administrators, without a password. Exploitation requires that a valid, unexpired passwordless login link (active for up to 7 days) exists for the target account at the time of the attack, and that the numeric link ID is known or guessable from the auto-increment primary key.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
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.8%
EPSS %ILE
54th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 8, 2026

Last Modified

July 8, 2026

Vendor Advisories for CVE-2026-14495(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 6× in last 7d / 36× 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.

Showing the most recent 100 of 227 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14495?
CVE-2026-14495 is a high vulnerability published on July 8, 2026. The DoLogin Security plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Randomness in all versions up to, and including, 4.3. The vulnerability exists because dologin\s::rrand() seeds the Mersenne Twister with mtsrand((double) microtime() * 1000000) — discarding the…
When was CVE-2026-14495 disclosed?
CVE-2026-14495 was first published on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14495 actively exploited?
CVE-2026-14495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14495?
CVE-2026-14495 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-14495?
No fix for CVE-2026-14495 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 vendor advisories EchelonGraph has for CVE-2026-14495 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14495?

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