Timeline for XSS Vulnerability Reproduction
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2019 at 17:05 | history | edited | roms | CC BY-SA 4.0 |
added 89 characters in body
|
| Sep 24, 2019 at 3:19 | answer | added | LTPCGO | timeline score: 1 | |
| Sep 23, 2019 at 15:45 | history | edited | roms | CC BY-SA 4.0 |
added 2015 characters in body
|
| Sep 18, 2019 at 23:16 | comment | added | LTPCGO | Try the URL via cURL or wget in a terminal of whatever OS you are using - the response looks the same except that your browser is encoding your request | |
| Sep 18, 2019 at 21:20 | review | Close votes | |||
| Oct 5, 2019 at 3:05 | |||||
| Sep 18, 2019 at 21:05 | comment | added | Ángel | How are you sending such request? Maybe with a browser that contains an anti-XSS? | |
| Sep 18, 2019 at 21:02 | comment | added | Arminius | Possible duplicate of Why isn't this XSS working? It's not an exact duplicate, but I'm quite sure the answer applies to your case too. | |
| Sep 18, 2019 at 20:57 | comment | added | RedS | Do you use the same headers as Qualys scanner do? Make sure You are reproducing full HTTP request, not just the URL one | |
| Sep 18, 2019 at 20:55 | review | First posts | |||
| Sep 18, 2019 at 23:16 | |||||
| Sep 18, 2019 at 20:51 | history | asked | roms | CC BY-SA 4.0 |