The vulnerability is a Cross-Site Request Forgery (CSRF) in the user settings update functionality. The analysis of the source code of the vulnerable version v2.0.15 revealed that the POST /settings/update endpoint, handled by the v2.BaseApi.UpdateSetting function, is responsible for updating user settings, including the username. The router configuration for this endpoint in core/router/ro_setting.go shows that it uses session-based authentication but lacks any CSRF protection, such as anti-CSRF tokens or SameSite cookie attributes. This allows an attacker to trick a logged-in administrator into unknowingly submitting a request to change their username, leading to an account lockout.