Using Custom HTML Tags to Run an XSS Attack

[@Lunamona-qp8cg]

You really deserve 1 million subscriber your explanation is great, Thank you sir!!

[@gopikanna_]

Thank you for the walkthrough

[@PrithibyCyberAcademy]

I love your teaching method.❤❤❤

[@youssefblt9839]

the explaination is on just mind blowing

[@adelaidemiguel9117]

Your videos on XSS are amazing, but you skipped some of the labs. So far you are the only one giving clear explanation. Please, if you may do series on XSS the whole word will appreciate. Thank you a lot.

[@z3nsh3ll]

Hey, don't worry, not skipping any - all remaining portswigger labs are coming soon.

[@toobaawan1402]

@@z3nsh3ll That's great. you really explain everything amazingly.

[@adelaidemiguel9117]

Good day Sir, thank you for your deep explanatory videos. How often do you release your videos? You made me fall in love with JS. I thought it was a very difficult script language.

[@z3nsh3ll]

Usually 2-3 vids per week. Releasing my CSS course at the moment, but I'll be back to creating more portswigger labs afterwards.

[@leghdaf]

Great Content ...

[@ochko7599]

why didn't you close your tag? And still it works

[@joeshmo546]

Spent way to much time on this and for some reason neither your solution or portswigger's solution work (i have adequately switched out the lab ids). Not sure if it's related but document.cookie seems to be blocked, but then again, the cookie didn't show up in you video either. Honestly clueless and frustrated over this one since the solution I came up with on my own is very similar to the "working" ones.

[@8Dbaybled8D]

remove the ; on the end of your location=''

[@myfreespirit]

It also happens to me from time to time in the labs that use an "exploit server". Usually waiting for the lab to expire and accessing a new LAB ID, solves the issue.