CVE-2026-86710

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

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

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

The Login with QR WordPress plugin through 1.0.0 does not verify that the code used to log a user in is one it issued, matching any stored user metadata value instead, which allows unauthenticated attackers to log in as any user, including administrators.

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

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (1)

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

Login with QR <= 1.0.0 – Unauthenticated Authentication Bypass via 'autologin_code' Parameter | CVE 2026-86710 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/d37dab2e-b137-4ad7-ab07-9c36b42a6485/

Vendor Advisories for CVE-2026-86710(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 28× in last 7d / 28× 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-09-20 04:56 UTCGHSA enrichment
  2. 2026-09-20 00:42 UTCGHSA enrichment
  3. 2026-09-19 20:30 UTCGHSA enrichment
  4. 2026-09-19 16:17 UTCEG score recompute
  5. 2026-09-19 16:17 UTCGHSA enrichment
  6. 2026-09-19 12:04 UTCGHSA enrichment
  7. 2026-09-19 07:51 UTCGHSA enrichment
  8. 2026-09-19 03:39 UTCGHSA enrichment
  9. 2026-09-18 23:26 UTCEG score recompute
  10. 2026-09-18 23:26 UTCGHSA enrichment
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 19:14 UTCGHSA enrichment
  13. 2026-09-18 15:28 UTCGHSA enrichment
  14. 2026-09-18 11:12 UTCGHSA enrichment
  15. 2026-09-18 06:59 UTCGHSA enrichment
  16. 2026-09-18 02:47 UTCGHSA enrichment
  17. 2026-09-17 22:34 UTCEG score recompute
  18. 2026-09-17 22:34 UTCGHSA enrichment
  19. 2026-09-17 19:32 UTCEPSS rescore
  20. 2026-09-17 18:18 UTCEG score recompute
  21. 2026-09-17 18:18 UTCGHSA enrichment
  22. 2026-09-17 13:22 UTCGHSA enrichment
  23. 2026-09-17 12:38 UTCEG score recompute▲ 9.80
  24. 2026-09-17 12:37 UTCGHSA enrichment
  25. 2026-09-17 12:34 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
Show 3 more
  1. 2026-09-17 06:23 UTCNVD update
  2. 2026-09-17 06:04 UTCEG score recompute
  3. 2026-09-17 06:04 UTCMITRE cvelistV5first tracked

Related CVEs

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2026-86710?
CVE-2026-86710 is a critical vulnerability published on September 17, 2026. The Login with QR WordPress plugin through 1.0.0 does not verify that the code used to log a user in is one it issued, matching any stored user metadata value instead, which allows unauthenticated attackers to log in as any user, including administrators.
When was CVE-2026-86710 disclosed?
CVE-2026-86710 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86710 actively exploited?
CVE-2026-86710 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 79.6% of all scored CVEs.
What is the CVSS score of CVE-2026-86710?
CVE-2026-86710 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-86710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86710, 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-86710

Explore →

Is Your Infrastructure Affected by CVE-2026-86710?

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

Start Free Scan →Browse All CVEs