The vulnerability exists in the password reset functionality of OneUptime. The application was logging the complete password reset URL, which includes the sensitive password reset token, at the INFO log level. Since INFO level is typically enabled in production environments, these tokens were exposed in application logs. An attacker with access to these logs could intercept a token and use it to reset a user's password, leading to account takeover. The analysis of the commits between the vulnerable version (10.0.22) and the patched version (10.0.24) revealed a commit that specifically addresses this issue. The commit 27ecf7625435823d36ea438dfca502b929fdb3ba changes the log level for the password reset URL from INFO to DEBUG in the file App/FeatureSet/Identity/API/Authentication.ts. The vulnerable function is the route handler for the POST /forgot-password endpoint, which contains the insecure logging statement. The patch confirms this by modifying the logger.info call to logger.debug, thus mitigating the vulnerability by default in production environments.