CyberRota Analysis
AI-GeneratedFlask-Security-Too version 5.8.0 is vulnerable due to an OAuth reauthentication flaw that allows an attacker to exploit a stale session of an authenticated user, effectively marking it as fresh after verifying their own OAuth identity. This could enable unauthorized access to sensitive account actions that rely on session freshness. Developers using this library in their Flask applications should prioritize upgrading to version 5.8.1 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
Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim session, they can complete OAuth verification using their own OAuth identity. The victim session is then treated as recently reauthenticated, allowing freshness-protected account actions to proceed. Version 5.8.1 contains a fix for this issue.