The vulnerability lies in the UsersRouter.handleVerificationEmailRequest function, which handles requests to the /verificationEmailRequest endpoint. Prior to the patch, this function would return different error responses depending on the status of the provided email address. Specifically, it would throw a Parse.Error.EMAIL_NOT_FOUND error if the email did not belong to any user, and a Parse.Error.OTHER_CAUSE error if the email was already verified. This discrepancy in responses allowed an attacker to enumerate valid, registered email addresses by observing the server's response to a series of requests. The provided patch introduces a new configuration option, emailVerifySuccessOnInvalidEmail, which is enabled by default. When enabled, the function returns a generic success response regardless of whether the email exists, is verified, or is invalid, thus preventing the enumeration attack. The analysis of the commit d3defb8 clearly shows the addition of conditional logic within UsersRouter.handleVerificationEmailRequest to return a generic response, directly addressing the information leak.