# CVE-2026-14291: Security Ninja (Premium) < 5.290 - Two-Factor Authentication Bypass via secnin_skip_2fa

> Unauthenticated attackers with valid passwords can bypass two-factor authentication in Security Ninja Premium, gaining unauthorized access to any account including administrators.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-8p8v-838m-f36p

## What is CVE-2026-14291?

CVE-2026-14291 is a high-severity authentication bypass vulnerability in Unknown security-ninja-premium, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-14291?


## How do I fix CVE-2026-14291?

No fix has been published for CVE-2026-14291 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14291 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14291 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14291 and fix it if it is affected.

What it is: CVE-2026-14291 is a high-severity authentication bypass vulnerability in Unknown security-ninja-premium, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14291 exists.

Affected product: Unknown security-ninja-premium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14291/ (Markdown: https://insights.sbomify.com/CVE-2026-14291/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14291
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14291
- OSV: https://osv.dev/vulnerability/CVE-2026-14291

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14291/
Summaries are generated and may contain mistakes; the official description above is the record.