14.7 Lab: CSRF where token is not tied to user session

A Simple writeup is posted on Medium - https://cyberw1ng.medium.com

Disclaimer:

The content shared in this video is intended for educational purposes only. The demonstrations, tutorials, and information presented are meant to highlight common vulnerabilities in cybersecurity systems and are performed in controlled environments, such as the Portswigger Labs, with explicit permission. The primary goal is to enhance knowledge and awareness of potential security threats and vulnerabilities.

Please be aware that attempting to exploit or replicate these techniques without proper authorization may violate applicable laws and regulations. The creator of this content does not encourage any illegal activities, and the responsibility for any misuse or consequences arising from these demonstrations lies solely with the viewer.

Always ensure that you have the appropriate permissions before conducting security testing on any system. It is recommended to seek professional advice and authorization from the relevant parties before attempting any penetration testing, ethical hacking, or security research.

The creator disclaims any liability for the misuse or misinterpretation of the information provided in this video. Viewers are encouraged to use this knowledge responsibly and ethically.

Description - Portswigger Lab
This lab's email change functionality is vulnerable to CSRF. It uses tokens to try to prevent CSRF attacks, but they aren't integrated into the site's session handling system. To solve the lab, use your exploit server to host an HTML page that uses a CSRF attack to change the viewer's email address | Karthikeyan Nagaraj

#cybersecurity #walkthrough #career