The vulnerability arises from the order of checks in the user_confirm() functions across authentication modules. Originally, these functions checked if the user was already confirmed before validating the authentication type. Attackers could exploit this by submitting confirmation requests for existing users, causing the system to return AUTH_CONFIRM_ALREADY even when the auth type was incorrect. This triggered the rendering of login/confirm.php, which displayed the user's full name via the removed fullname($user) line. The patch reordered the checks to validate the auth type first, preventing unauthorized confirmation status leaks. The high confidence stems from the direct linkage between the flawed logic in these functions and the exposure mechanism described in the CVE.