CVE-2026-14291

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
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 security-ninja-premium WordPress plugin before 5.290 does not verify the second authentication factor in one of its two-factor authentication code paths, allowing an unauthenticated attacker who knows a user's password to complete authentication without the one-time code and bypass enforced two-factor authentication for any account, including administrators. The affected two-factor module ships only in the premium build.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

Security Ninja (Premium) < 5.290 – Two-Factor Authentication Bypass via secnin_skip_2fa | CVE 2026-14291 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/e62cfba9-4956-43ba-8554-6cdb0eb8815b/

Vendor Advisories for CVE-2026-14291(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 24× in last 7d / 32× 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 13:50 UTCGHSA enrichment
  2. 2026-07-31 00:49 UTCEG score recompute
  3. 2026-07-31 00:49 UTCGHSA enrichment
  4. 2026-07-30 16:27 UTCEPSS rescore
  5. 2026-07-30 11:48 UTCEG score recompute
  6. 2026-07-30 11:48 UTCGHSA enrichment
  7. 2026-07-30 01:30 UTCEPSS rescore
  8. 2026-07-29 22:42 UTCGHSA enrichment
  9. 2026-07-29 09:38 UTCGHSA enrichment
  10. 2026-07-28 20:37 UTCEG score recompute
  11. 2026-07-28 20:37 UTCGHSA enrichment
  12. 2026-07-28 15:36 UTCEPSS rescore
  13. 2026-07-28 07:36 UTCGHSA enrichment
  14. 2026-07-27 18:32 UTCEG score recompute
  15. 2026-07-27 18:32 UTCGHSA enrichment
  16. 2026-07-27 14:13 UTCEPSS rescore
  17. 2026-07-27 05:31 UTCGHSA enrichment
  18. 2026-07-26 16:22 UTCEG score recompute
  19. 2026-07-26 16:22 UTCGHSA enrichment
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 03:21 UTCEG score recompute
  23. 2026-07-26 03:21 UTCGHSA enrichment
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
Show 7 more
  1. 2026-07-23 14:57 UTCEG score recompute▲ 7.50
  2. 2026-07-23 14:57 UTCGHSA enrichment
  3. 2026-07-23 14:56 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 07:50 UTCNVD update
  6. 2026-07-23 06:45 UTCEG score recompute
  7. 2026-07-23 06:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14291?
CVE-2026-14291 is a high vulnerability published on July 23, 2026. The security-ninja-premium WordPress plugin before 5.290 does not verify the second authentication factor in one of its two-factor authentication code paths, allowing an unauthenticated attacker who knows a user's password to complete authentication without the one-time code and bypass enforced…
When was CVE-2026-14291 disclosed?
CVE-2026-14291 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14291 actively exploited?
CVE-2026-14291 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 74.8% of all scored CVEs.
What is the CVSS score of CVE-2026-14291?
CVE-2026-14291 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14291?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14291, 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-14291

Explore →

Is Your Infrastructure Affected by CVE-2026-14291?

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

Start Free Scan →Browse All CVEs