Anti-CSRF Token From Referer

Working

The extension works by registering a new session handling rule called "Anti-CSRF token from referer". This handler inspects all the requests and searches for the anti-CSRF token parameter (in GET, POST, JSON and multipart requests) determine$

Once this parameter is found, a GET request is issued to the referer of the original request. In this request, all the headers are copied from the original request (e.g Cookie, Authorization...).

This response is then parsed and the substring between the start and the end markers configured in the tab is extracted as the anti-CSRF token.

Finally, the anti-CSRF token is replaced in the original request.

Usage

1. Create a new session handling rule (Invoke a Burp extension > Anti-CSRF token from referer)
2. Define session scope
3. Configure parameters in Anti-CSRF token from referer tab

For further information, consult the documentation on https://github.com/CompassSecurity/anti-csrf-token-from-referer/blob/master/README.md