Step #1: Configure your browser to work through Burp as a proxy.
Step #2: Browse and login to the area of the application your testing for CSRF. For this example, we’re using the login form fields. *Note that CSRF can be an issue in many places of an application, not just the login process.
Step #3: In Burp, browse to the POST that was recorded with your username and password (Status 302).
Step #4: Right-click on the POST and choose Engagement tools->Generate CSRF PoC.
Step #5: Next, click the Test in browser button. And then the Copy button.
Step #6: Clear the cache in your browser, and then paste the URL into your browser. And click on the Submit request button.
Step #7: If your application is susceptible to CSRF, you will now be successfully logged into the application under the user’s account.
So how do you fix this issue? For this login scenario, the best way is to introduce a Nonce or a Salted Password Hash during the POST process. Anything that generates a random ‘identifier’ per request can help mitigate the issue. Good luck CSRF-ing.