The vulnerability stems from the absence of session validation checks for user account status (enabled/disabled) during subsequent requests. The fix introduced a new middleware (VerifyUserEnabled) that checks if the authenticated user is still enabled. In vulnerable versions (<22.10.0), this middleware was missing, allowing sessions to remain valid even after account disablement. While session management functions (Auth::logout(), session invalidation) exist in Laravel's core, the specific vulnerability arises from the lack of integration of these functions with user status checks in the application's middleware stack, not from inherently vulnerable functions themselves.