Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10293: CWE-287 Improper Authentication in nexist Keyy Two Factor Authentication (like Clef)

0
High
VulnerabilityCVE-2025-10293cvecve-2025-10293cwe-287
Published: Wed Oct 15 2025 (10/15/2025, 08:25:50 UTC)
Source: CVE Database V5
Vendor/Project: nexist
Product: Keyy Two Factor Authentication (like Clef)

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.

AI-Powered Analysis

AILast updated: 10/15/2025, 08:53:28 UTC

Technical Analysis

CVE-2025-10293 identifies a critical improper authentication vulnerability (CWE-287) in the Keyy Two Factor Authentication plugin for WordPress, a plugin designed to enhance login security by adding a 2FA layer similar to Clef. The vulnerability exists in all versions up to and including 1.2.3. The root cause is the plugin's failure to properly validate the user identity associated with generated authentication tokens. As a result, an attacker who is already authenticated with subscriber-level or higher privileges can generate valid authentication tokens arbitrarily. This allows the attacker to bypass the intended 2FA protections and automatically log in as other users, including administrators who have 2FA enabled. The exploit requires no user interaction and can be performed remotely over the network, making it highly accessible to attackers with low privileges. The impact includes full account takeover, privilege escalation, and potential site-wide compromise, affecting confidentiality, integrity, and availability of the WordPress environment. Although no public exploits have been reported yet, the vulnerability's characteristics and CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicate a high likelihood of exploitation and severe consequences. The vulnerability was reserved in September 2025 and published in October 2025, with no patches currently available, increasing urgency for mitigation. The plugin is widely used in WordPress deployments, which are prevalent in Europe, especially among small and medium enterprises and public sector websites.

Potential Impact

For European organizations, this vulnerability poses a significant threat to websites and web applications running WordPress with the Keyy Two Factor Authentication plugin. Successful exploitation leads to unauthorized administrative access, enabling attackers to manipulate website content, steal sensitive data, deploy malware, or disrupt services. This can result in data breaches, reputational damage, regulatory non-compliance (e.g., GDPR violations), and operational downtime. Organizations relying on WordPress for customer portals, intranets, or e-commerce platforms are particularly vulnerable. The ease of exploitation by low-privilege authenticated users increases insider threat risks and the potential for lateral movement within networks. Given the widespread use of WordPress in Europe, the vulnerability could affect a broad range of sectors, including government, finance, healthcare, and education. The lack of available patches at the time of disclosure further exacerbates the risk, necessitating immediate compensating controls to protect critical assets.

Mitigation Recommendations

1. Immediately audit WordPress installations to identify the presence of the Keyy Two Factor Authentication plugin and its version. 2. If possible, disable or uninstall the plugin until a secure patch is released. 3. Restrict subscriber-level user privileges to the minimum necessary to reduce the risk of exploitation. 4. Implement additional authentication layers such as IP whitelisting, VPN access, or hardware-based 2FA for administrative accounts. 5. Monitor authentication logs for unusual token generation or login patterns indicative of abuse. 6. Apply web application firewall (WAF) rules to detect and block suspicious requests targeting the plugin’s authentication endpoints. 7. Educate administrators and users about the vulnerability and encourage strong password policies to limit account compromise. 8. Stay informed about vendor updates and apply patches promptly once available. 9. Consider alternative 2FA plugins with verified security track records as a temporary replacement. 10. Conduct penetration testing and vulnerability assessments focused on authentication mechanisms to identify residual risks.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-11T19:45:14.095Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ef5c7cc4f69c9730e56970

Added to database: 10/15/2025, 8:34:04 AM

Last enriched: 10/15/2025, 8:53:28 AM

Last updated: 10/15/2025, 1:14:47 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats