# CVE-2025-10293: Auth bypass in Keyy Two Factor Authentication (like Clef)

> Authenticated attackers can bypass two-factor authentication to take over administrator accounts if 2FA is enabled.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jr4v-gcqw-x774

## What is CVE-2025-10293?

CVE-2025-10293 is a high-severity authentication bypass vulnerability in nexist Keyy Two Factor Authentication (like Clef), published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Keyy Two Factor Authentication (like Clef) plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.2.3. This is due to the plugin not properly validating a user's identity associated with a token generated. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate valid auth tokens and leverage that to auto-login as other accounts, including administrators, as long as the administrator has the 2FA set up.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-10293?


## How do I fix CVE-2025-10293?

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

## Is CVE-2025-10293 being exploited?

There is no known exploitation of CVE-2025-10293 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10293 and fix it if it is affected.

What it is: CVE-2025-10293 is a high-severity authentication bypass vulnerability in nexist Keyy Two Factor Authentication (like Clef), published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10293 in the wild and no public exploit code.

Affected product: nexist Keyy Two Factor Authentication (like Clef). 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-2025-10293/ (Markdown: https://insights.sbomify.com/CVE-2025-10293/index.md)
```

## Sources

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

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