[PortSwigger][Practitioner] - Lab: CSRF where token is not tied to user session
In this lab, the vulnerability was Cross-Site Request Forgery (CSRF), caused by a lack of proper synchronization between the CSRF token and user sessions. The application issued CSRF tokens for all requests without tying them to active user sessions, allowing an attacker to exploit unintended actions on behalf of the victim. The researcher used Burp Suite's Intruder tool to inject a malicious payload into a victim's browser through a phishing email or other means. By exploiting this flaw, the attacker could execute unwanted account changes or data manipulation, as the application accepted user requests without verifying their origin. The impact included unauthorized actions and potential privacy breaches. Remediation includes tying CSRF tokens to active user sessions during token generation. Key lesson: Always ensure proper synchronization between CSRF tokens and user sessions to prevent CSRF attacks. #BugBounty #Cybersecurity #WebSecurity #CSRF #InputValidation


