Reflected XSS in a JavaScript URL with some characters blocked - Explaining the Payload

[@pinkypink2410]

This is extremely helpful! I am not really familiar enough with js, but i really wanted to understand this lab, and it would be so bad without your explanation. Thank you million times!

[@normalitee0os]

JUST ABSOLUTE CRAZY EXPLAINATION! SUPER SIMPLIFIED!!!

[@sabarishAB-y3o]

Best Explanation Ever !!! Really Crazy and very simple to understand and I wish you the very Best !!!

[@Mr.Manimal]

Really well done course! Thanks for your content!

[@pv7523]

Dude, This is really great, You are clearly explaining with custom code, thank you

[@Sofi-ps5zc]

Really amazing and detailed explanation! Thank you!

[@wafflesexploit]

Thank you so much for this video, everysince I found your channel you have been my savior to understand some of the experts labs. So really thank you so muchh!!!!!!

[@YousefAmmar-t6d]

Absolutely splendid explanation, thank you so much

[@mohsinhafeez]

BEAUTIFULLY explained, thank you very much!

[@akemi-ih1ky]

Thanks a lot! detailed and clear, satisfactory indeed.

[@mohammedeleriaan5986]

Ultimate Explanation

[@bilal3zdin]

the best one to explain it
keep going

[@TestoWitschz]

Thank you for that video!

[@DaniilKozyr]

Wow! You are the best!

[@PinkBatman566]

This is so useful thank you

[@YoussefAlsalahy]

perfect explanation keep going

[@fezzaalamriyaakoub]

Thank you very much for the video.

[@scharfer56]

Thank you! There is one thing that I would like explained. When you pass in the correct query param to solve the lab, and you look at the HTML of the returned response, it does not look like the code passed in the query string was successfully injected. e.g. you do not see an actual single quote to close the value of the body property in the fetch payload. Instead, you see an encoded single quote, which is not valid javascript.
I guess the browser decodes the javascript url before executing it, but I do wonder about that.

[@neadlead2621]

have the same question

[@neadlead2621]

the payload in this case will go into href ,which means a url ; and encoding in this case is ok

[@ogmol11]

thanks for this explanation.

[@pranjalruhela1103]

I could see the reflection point in the source.... that's it then I am here.......THANKS for the video..,...I still couldn't understand why the tostring and window are required in our payload...

[@z3nsh3ll]

The main reason we have to use window and toString is in order to execute our function. We can't execute a function directly using function scopes () because they are blocked by the page.

[@pranjalruhela1103]

@@z3nsh3ll Got it!

[@horrornation9391]

thanks for sharing this information.

[@Linnocks]

you are the best man

[@ossamayasser1242]

Thanks for this great explaination♥
I have a question, how does the javascript worked while the equal signs are encoded?

[@aaronaguilar2238]

Great video! 🎉

[@bilal3zdin]

does the fetch function unicode the url body automaticly ?

[@neadlead2621]

Nice one I have 1 question and one comment , the question is that how the xss happens when the url is encoded and the payload is also encoded ,and the comment is that it's not the parameter that is vulnerable but the url being reflected in the page

[@neadlead2621]

A response for my self the payload in this case will go into href which means a url and encoding in this case is ok

[@acronproject]

Thanks a lot for this

[@Amit-fn7bw]

thanks for this video

[@Duskk0077]

great man thanks

[@germanmalinovsky1719]

brilliant

[@iss9796]

awesome. great

[@aymanrbati531]

Dope