CVE-2026-65570

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

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

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

Unauthenticated Bypass Vulnerability in Login with phone number <= 1.8.70 versions.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

Bypass Vulnerability in WordPress Login with phone number Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/login-with-phone-number/vulnerability/wordpress-login-with-phone-number-plugin-1-8-70-bypass-vulnerability-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-65570(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 / 55× 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 07:24 UTCGHSA enrichment
  2. 2026-08-19 18:50 UTCEG score recompute
  3. 2026-08-19 18:50 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 04:16 UTCGHSA enrichment
  6. 2026-08-18 15:42 UTCEG score recompute
  7. 2026-08-18 15:42 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 02:49 UTCGHSA enrichment
  10. 2026-08-17 14:14 UTCEG score recompute
  11. 2026-08-17 14:14 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 01:40 UTCEG score recompute
  14. 2026-08-17 01:40 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 13:05 UTCEG score recompute
  17. 2026-08-16 13:05 UTCGHSA enrichment
  18. 2026-08-16 00:31 UTCGHSA enrichment
  19. 2026-08-15 11:57 UTCEG score recompute
  20. 2026-08-15 11:57 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 23:22 UTCGHSA enrichment
  23. 2026-08-14 10:48 UTCGHSA enrichment
  24. 2026-08-13 22:14 UTCEG score recompute
  25. 2026-08-13 22:14 UTCGHSA enrichment
Show 30 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 09:39 UTCGHSA enrichment
  3. 2026-08-12 21:05 UTCGHSA enrichment
  4. 2026-08-12 16:41 UTCEG score recompute
  5. 2026-08-12 16:41 UTCGHSA enrichment
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-12 04:07 UTCGHSA enrichment
  8. 2026-08-11 15:32 UTCEG score recompute
  9. 2026-08-11 15:32 UTCGHSA enrichment
  10. 2026-08-11 02:58 UTCEG score recompute
  11. 2026-08-11 02:58 UTCGHSA enrichment
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-10 14:24 UTCGHSA enrichment
  14. 2026-08-10 01:49 UTCEG score recompute
  15. 2026-08-10 01:49 UTCGHSA enrichment
  16. 2026-08-09 13:47 UTCEPSS rescore
  17. 2026-08-09 13:15 UTCGHSA enrichment
  18. 2026-08-09 00:41 UTCEG score recompute
  19. 2026-08-09 00:41 UTCGHSA enrichment
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 12:07 UTCGHSA enrichment
  22. 2026-08-07 23:33 UTCEG score recompute
  23. 2026-08-07 23:33 UTCGHSA enrichment
  24. 2026-08-07 10:58 UTCEG score recompute
  25. 2026-08-07 10:58 UTCGHSA enrichment
  26. 2026-08-06 22:23 UTCEG score recompute
  27. 2026-08-06 22:23 UTCGHSA enrichment
  28. 2026-08-06 15:27 UTCEG score recompute
  29. 2026-08-06 14:43 UTCEG score recompute
  30. 2026-08-06 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65570?
CVE-2026-65570 is a high vulnerability published on August 6, 2026. Unauthenticated Bypass Vulnerability in Login with phone number <= 1.8.70 versions.
When was CVE-2026-65570 disclosed?
CVE-2026-65570 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65570 actively exploited?
CVE-2026-65570 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-65570?
CVE-2026-65570 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-65570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65570, 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-65570

Explore →

Is Your Infrastructure Affected by CVE-2026-65570?

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

Start Free Scan →Browse All CVEs