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-10305: CWE-862 Missing Authorization in endisha Secure Passkeys

0
Medium
VulnerabilityCVE-2025-10305cvecve-2025-10305cwe-862
Published: Sat Sep 20 2025 (09/20/2025, 04:27:55 UTC)
Source: CVE Database V5
Vendor/Project: endisha
Product: Secure Passkeys

Description

The Secure Passkeys plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the delete_passkey() and passkeys_list() function in all versions up to, and including, 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view and delete passkeys.

AI-Powered Analysis

AILast updated: 09/28/2025, 00:47:11 UTC

Technical Analysis

CVE-2025-10305 is a vulnerability identified in the Secure Passkeys plugin for WordPress, developed by endisha. The vulnerability arises from a missing authorization check (CWE-862) in two critical functions: delete_passkey() and passkeys_list(). These functions are responsible for managing passkeys, which are authentication credentials used to enhance login security. Due to the lack of proper capability checks, any authenticated user with Subscriber-level access or higher can exploit this flaw to view and delete passkeys belonging to other users. This unauthorized access does not require elevated privileges beyond Subscriber, which is typically the lowest level of authenticated access in WordPress. The vulnerability affects all versions of the plugin up to and including version 1.2.1. The CVSS v3.1 base score is 5.3, indicating a medium severity level. The vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) suggests that the attack can be performed remotely over the network with low attack complexity, no privileges required beyond authentication, and no user interaction needed. The impact is limited to integrity, as attackers can delete or manipulate passkeys but cannot directly compromise confidentiality or availability. No known exploits are currently reported in the wild, and no patches have been linked yet. This vulnerability could allow attackers to disrupt user authentication mechanisms by deleting passkeys, potentially forcing users to reset credentials or lose access, and could also facilitate further attacks if passkeys are exposed or manipulated.

Potential Impact

For European organizations using WordPress sites with the Secure Passkeys plugin, this vulnerability poses a moderate risk. Attackers with minimal authenticated access (Subscriber-level) can manipulate authentication credentials, undermining the integrity of user authentication. This could lead to unauthorized account access if attackers delete or tamper with passkeys, forcing users to re-register or potentially enabling attackers to bypass multi-factor authentication mechanisms. Organizations relying on WordPress for critical services or customer-facing portals could face disruption, loss of user trust, and potential compliance issues under GDPR if user authentication is compromised. The impact is particularly significant for sectors with stringent security requirements, such as finance, healthcare, and government, where authentication integrity is paramount. However, since exploitation requires authenticated access, the threat is somewhat mitigated by existing access controls and monitoring. Still, insider threats or compromised low-privilege accounts could leverage this vulnerability to escalate attacks.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should immediately audit their WordPress installations for the presence of the Secure Passkeys plugin and verify the version in use. Until an official patch is released, administrators should consider temporarily disabling the plugin or restricting access to Subscriber-level accounts to trusted users only. Implementing strict user role management and monitoring for unusual Subscriber-level activity can help detect exploitation attempts. Additionally, organizations should enforce strong authentication policies, including multi-factor authentication for all users, to reduce the risk of account compromise. Reviewing and hardening WordPress user permissions and employing security plugins that monitor unauthorized changes to authentication credentials can provide additional layers of defense. Once a patch becomes available, prompt application is critical. Regular backups of authentication data and passkeys should be maintained to enable recovery in case of deletion or tampering.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-11T22:04:22.079Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68cf42444a0b186b9321b040

Added to database: 9/21/2025, 12:09:40 AM

Last enriched: 9/28/2025, 12:47:11 AM

Last updated: 11/4/2025, 11:40:42 PM

Views: 60

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