CVE-2026-12988

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

Score 6.4 from GitHub Security Advisory published 2026-07-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: Elevated riskExposed: 0

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

The WP 2FA WordPress plugin before 3.1.1.2 does not verify that the email address supplied during two-factor authentication setup belongs to the user, allowing an attacker who has obtained a user's credentials to redirect the setup verification code to an attacker-controlled email address and take over the account.

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

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

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

WP 2FA < 3.1.1.2 – Account Takeover via 2FA Setup Email Binding | CVE 2026-12988 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/8aa6bf91-54ee-4326-a477-31f42284be22/

Vendor Advisories for CVE-2026-12988(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 19× 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.

  1. 2026-07-31 07:19 UTCEG score recompute
  2. 2026-07-31 07:19 UTCGHSA enrichment
  3. 2026-07-30 16:27 UTCEPSS rescore
  4. 2026-07-30 08:13 UTCEG score recompute
  5. 2026-07-30 08:13 UTCGHSA enrichment
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-29 09:02 UTCEG score recompute
  8. 2026-07-29 09:02 UTCGHSA enrichment
  9. 2026-07-28 15:36 UTCEPSS rescore
  10. 2026-07-28 09:58 UTCEG score recompute
  11. 2026-07-28 09:58 UTCGHSA enrichment
  12. 2026-07-27 14:13 UTCEPSS rescore
  13. 2026-07-27 10:53 UTCEG score recompute
  14. 2026-07-27 10:53 UTCGHSA enrichment
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 11:50 UTCEG score recompute
  18. 2026-07-26 11:49 UTCGHSA enrichment
  19. 2026-07-25 14:17 UTCEPSS rescore
  20. 2026-07-24 14:17 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:05 UTCEG score recompute
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 11 more
  1. 2026-07-19 14:30 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-17 01:43 UTCEG score recompute▲ 6.40
  4. 2026-07-17 01:43 UTCGHSA enrichment
  5. 2026-07-16 17:02 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-14 12:40 UTCMITRE cvelistV5CVSS v3 → 6.4 · severity → MEDIUM
  9. 2026-07-14 07:16 UTCNVD update
  10. 2026-07-14 06:05 UTCEG score recompute
  11. 2026-07-14 06:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12988?
CVE-2026-12988 is a medium vulnerability published on July 14, 2026. The WP 2FA WordPress plugin before 3.1.1.2 does not verify that the email address supplied during two-factor authentication setup belongs to the user, allowing an attacker who has obtained a user's credentials to redirect the setup verification code to an attacker-controlled email address and take…
When was CVE-2026-12988 disclosed?
CVE-2026-12988 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12988 actively exploited?
CVE-2026-12988 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 93.4% of all scored CVEs.
What is the CVSS score of CVE-2026-12988?
CVE-2026-12988 has a CVSS v3.1 base score of 6.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12988?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12988, 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-12988

Explore →

Is Your Infrastructure Affected by CVE-2026-12988?

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

Start Free Scan →Browse All CVEs