-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XSS Reorganization #591
Comments
This comment has been minimized.
This comment has been minimized.
I would like to be work on this. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Please comment if you are still working on this issue, as it has been inactive for 90 days. To give everyone a chance to contribute, we are releasing it to new contributors. |
I can do this, since they still seem to be in separate chapters. |
Hows this for order? Unless you just wanted 7 added to the end of chapter 11
|
No no, to be clear XSS is the only thing that's moving. Any XSS scenarios that are currently in section 7 should move to section 11. 01-Testing_for_Reflected_Cross_Site_Scripting.md Should move into a unified XSS section with DOM in 11. Something like: 01-Testing_for_Reflected_Cross_Site_Scripting.md or 01 Testing for Cross Site Scripting Something along those lines. Have a look at it, have a look at how SQLi is done since this could be similar. |
^ edited: had further thoughts 😉 |
Ok great, thanks for the clarification! I'm double-checking section 7 now |
I deleted my last comment, was looking at the wrong tab! |
Those are already in 11 👍 |
Yeah, there was a sudden bit of chaos in the house and I realized with the distraction I'd been looking at 11 not 7 |
All good, been there. |
…ameter_Pollution (OWASP#591)
…ameter_Pollution (OWASP#591)
…Testing/03.2-Testing_for_MySQL (OWASP#591)
…Testing/06-Testing_for_SSI_Injection (OWASP#591)
…Testing/06-Testing_for_SSI_Injection (OWASP#591)
…Testing/08-Testing_for_IMAP_SMTP_Injection (OWASP#591)
…Testing/09.1-Testing_for_File_Inclusion (OWASP#591)
…Testing/10-Testing_for_Command_Injection (OWASP#591)
…Testing/12-Testing_for_Format_String_Injection (OWASP#591)
…Testing/13-Testing_for_Incubated_Vulnerability (OWASP#591)
…Testing/14-Testing_for_HTTP_Splitting_Smuggling (OWASP#591)
…alidation_Testing/16-Testing_for_Host_Header_Injection (OWASP#591)
…lidation_Testing/17-Testing_for_Server-side_Template_Injection (OWASP#591)
…lidation_Testing/18-Testing_for_Server-Side_Request_Forgery (OWASP#591)
…Testing/19-Testing_for_Mass_Assignment (OWASP#591)
…ng/01.1-Testing_for_Reflected_Cross_Site_Scripting (OWASP#591)
…ng/01.2-Testing_for_Stored_Cross_Site_Scripting (OWASP#591)
…ng/01.4-Testing_for_Self_DOM_Based_Cross_Site_Scripting (OWASP#591)
…07-Input_Validation_Testing/03-Testing_for_SQL_Injection (OWASP#591)
What's the current setup?
Reviewing XSS overall in the document, it's split into 2 different chapters, 7 and 11.
At the end of the day, all XSS will target users on the client-side, even if it was stored.
What would you like to happen?
Move all XSS to chapter 11, client-side testing, and have one big section for XSS and then going into more tests for other types of testing.
What do you guys think?
The text was updated successfully, but these errors were encountered: