The csrf token remains same after user logs in

###Description As the CSRF token doesn't change after login. Any other user that uses the same workstation is vulnerable. A safer way would be to use dynamic CSRF token or just change the token after login, so attacker doesn't get hold of this. ### Details of the attacks scenario in a shared workstation environment 1. The attacker simply copies the authenticity token. This token is the only protection against the CSRF attack. 2. Any other user that uses the workstation after that is vulnerable to CSRF. The attacker simply needs to craft a link with the required GET or POST method as he already have the CSRF token and send it to the victim via email, chat etc. 3. he attacker can trick the victim in doing anything he wants without the user being aware of it. ## Impact Any other user that uses the same workstation is vulnerable to CSRF attack