CVE-2025-10293
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Keyy Two Factor Authentication plugin for WordPress fails to properly validate user identity associated with generated authentication tokens. Authenticated attackers with subscriber-level access can generate valid 2FA tokens and use them to auto-login as other users, including administrators who have enabled 2FA, due to insufficient identity validation in the token consumption flow.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Keyy plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate the Keyy Two Factor Authentication plugin. Note the installed version number.Affected if The installed version is earlier than 1.2.4 (the patched version).
-
Confirm 2FA is actively enabledNavigate to the Keyy plugin settings or check user profiles to verify that two-factor authentication is enabled for at least some user accounts on the site.Affected if 2FA is enabled for any user account, particularly administrator accounts, as these are the likely targets of token hijacking.
-
Identify low-privilege user accountsGo to Users > All Users and review the role distribution. Check for any subscriber-level accounts or other low-privilege users that should not have access.Affected if There are subscriber-level or low-privilege user accounts present that could potentially exploit the insufficient token identity validation.
-
Review authentication logs for anomalous 2FA token usageCheck WordPress debug logs, server access logs, or any security plugin logs for 2FA token generation and consumption events. Look for patterns where tokens were generated by one user but consumed by another.Affected if Logs show 2FA tokens generated by subscriber accounts being used to authenticate as different users, particularly administrators.
You are affected if the Keyy plugin version is below 1.2.4 and 2FA is enabled on the site, especially if low-privilege subscriber accounts exist that could exploit the token identity validation flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Keyy plugin to version 1.2.4 or later which contains the fix for proper token identity validation; if no patched version exists, disable the plugin and migrate to an alternative reputable 2FA solution.
Version greater than 1.2.3 (check wordpress.org for the specific patched release)
- Check the WordPress plugin repository or Wordfence advisory for the Keyy Two Factor Authentication plugin to identify the current fixed version
- If a fixed version (greater than 1.2.3) is available, navigate to WordPress admin dashboard > Plugins
- Deactivate and delete the vulnerable Keyy Two Factor Authentication plugin
- Install the fixed version of the plugin from the WordPress plugin repository
- Reactivate the plugin and verify the Two-Factor Authentication functionality works correctly
- Ensure all administrator accounts re-configure their 2FA settings after the upgrade to ensure secure token binding
- Audit user accounts for any unauthorized access attempts that may have occurred during the vulnerability window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data