Answer received! Your answer was received and will be reviewed. Be sure to keep an eye on your email to check the status.
Error! Your answer was not received. Please make sure all required fields are filled in.
Important information
Challenges do NOT require any bruteforcing/directory fuzzing/massive amounts of traffic unless clearly specified in the challenge information below.
Challenge Information
This one will require a bit of thinking. It's designed to be a complete blackbox so you have no idea what it's looking for but using information on the page and basic understanding of HTTP requests you should be able to work it out.
The aim of this challenge is to execute XSS via [something] (revealed in hints)
 
Challenge Solutions
Important: We can see you don't have a valid submission to this challenge yet. Be warned you may ruin the challenge by viewing the solution
Not everyone thinks about injecting XSS into the referrer, but this challenge made sure you did think about it! Aside from the fact it was a complete blackbox and you had to guess to use ?debug mode, the answer relies in the Referer header.
If ?debug was enabled, it would then respond back with information relating to the request in which it gives you hints where the request came from. If the request had no referer or was from bugbountytraining, it says "debug mode is on but request appeared ok
". The idea was to start fuzzing around the HTTP request (keyword being request) to see what it was doing with it.