In this walk through, we will be going through the Cross Site Scripting Reflected (HREF) vulnerability section from bWAPP Labs. We will be exploring and exploiting Reflected Cross Scripting vulnerability in HREF implementations and learn how application are affected because of it. So, let’s get started with the Hacking without any delay.
Table of Contents
Security: Low
- Setting the security level to Low.
- The application has a page to enter the user name as input to vote for their favorite movie. In the next page, There is a list of movies and one can cast vote against his their favorite one. As we can see as per the DOM structure the name is getting stored inside it to display on another page and then passed to other requests as well. Once Voted, a last page where submission is visible to the user.
- I intercepted the request via Burpsuite from first page to second and manipulated the request to change the name value to my below payload. Upon Forwarding the request, i receive a pop-up alert.
><script>alert("Hacked")</script><
- Not working in Medium and High level.
Also Read: bWAPP – Cross Site Scripting Reflected (POST)
Conclusion:
So, we finally completed all the security levels for the bWAPP Cross Site Scripting Reflected (HREF) Vulnerability. We looked into the various ways how application has been set up in various levels and how we can bypass the security controls implemented. Reflected-XSS attacks can be mitigated by performing input sanitization on endpoints, whitelist the allowed characters in the input and using a WAF. Along with that, we can prevent data from any untrusted source to be dynamically written to the HTML document. On that note, i will take your leave and will meet you in next one with another bWAPP vulnerability writeup, till then “Keep Hacking”.
