CVE-2026-16619

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

The miniOrange 2FA WordPress plugin before 6.2.8 does not correctly limit the number of second-factor verification attempts, tracking them against a client-supplied identifier that is reissued on every login, allowing an attacker who already knows a user's password to guess the one-time code without limit and take over the account.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
50(Track*)
EG Risk 50/100SSVC: Track*

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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

miniOrange 2FA < 6.2.8 – 2FA Bypass via Unlimited Second-Factor Attempts | CVE 2026-16619 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/54fc1229-3e68-4d21-baec-59a44cf12a65/

Vendor Advisories for CVE-2026-16619(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 26× in last 7d / 60× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:54 UTCGHSA enrichment
  3. 2026-08-20 09:41 UTCGHSA enrichment
  4. 2026-08-19 21:27 UTCEG score recompute
  5. 2026-08-19 21:27 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 09:04 UTCGHSA enrichment
  8. 2026-08-18 20:47 UTCEG score recompute
  9. 2026-08-18 20:47 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 08:33 UTCGHSA enrichment
  12. 2026-08-17 20:12 UTCEG score recompute
  13. 2026-08-17 20:12 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 07:55 UTCGHSA enrichment
  16. 2026-08-16 19:42 UTCEG score recompute
  17. 2026-08-16 19:42 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 07:28 UTCEG score recompute
  20. 2026-08-16 07:28 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 19:15 UTCGHSA enrichment
  23. 2026-08-15 07:01 UTCEG score recompute
  24. 2026-08-15 07:01 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 35 more
  1. 2026-08-14 18:47 UTCGHSA enrichment
  2. 2026-08-14 06:34 UTCEG score recompute
  3. 2026-08-14 06:34 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 18:20 UTCGHSA enrichment
  6. 2026-08-13 06:05 UTCGHSA enrichment
  7. 2026-08-12 17:51 UTCEG score recompute
  8. 2026-08-12 17:51 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-12 05:38 UTCGHSA enrichment
  11. 2026-08-11 17:22 UTCEG score recompute
  12. 2026-08-11 17:22 UTCGHSA enrichment
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 05:01 UTCEG score recompute
  15. 2026-08-11 05:01 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 16:48 UTCGHSA enrichment
  18. 2026-08-10 04:35 UTCGHSA enrichment
  19. 2026-08-09 16:21 UTCEG score recompute
  20. 2026-08-09 16:21 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 04:08 UTCEG score recompute
  23. 2026-08-09 04:08 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 15:55 UTCGHSA enrichment
  26. 2026-08-08 03:41 UTCEG score recompute
  27. 2026-08-08 03:41 UTCGHSA enrichment
  28. 2026-08-07 15:27 UTCEG score recompute
  29. 2026-08-07 15:27 UTCGHSA enrichment
  30. 2026-08-07 14:38 UTCEG score recompute
  31. 2026-08-07 14:38 UTCGHSA enrichment
  32. 2026-08-07 10:30 UTCEG score recompute
  33. 2026-08-07 10:30 UTCGHSA enrichment
  34. 2026-08-06 22:16 UTCEG score recompute
  35. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16619?
CVE-2026-16619 is a high vulnerability published on August 6, 2026. The miniOrange 2FA WordPress plugin before 6.2.8 does not correctly limit the number of second-factor verification attempts, tracking them against a client-supplied identifier that is reissued on every login, allowing an attacker who already knows a user's password to guess the one-time code…
When was CVE-2026-16619 disclosed?
CVE-2026-16619 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16619 actively exploited?
CVE-2026-16619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-16619?
CVE-2026-16619 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-16619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16619, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16619?

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

Start Free Scan →Browse All CVEs