CyberRota Analysis
AI-GeneratedLogto's Account Center prior to version 1.41.0 is vulnerable to unauthorized MFA factor management due to improper verification of user identity, allowing an attacker with an active bearer token to create and verify a WebAuthn registration without needing to prove possession of any existing credentials. This high-severity vulnerability could lead to account takeover and unauthorized access to sensitive resources. Organizations using Logto for authentication should prioritize upgrading to version 1.41.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.