Describe the bug
The "Customize HTML Report Option" is missing the evidence field which is necessary for the receiver of the report to know where they need to solve the issue.

In this example, the HTML source code of the page is several thousand lines of code the report is Reverse Tabnabbing so the developer will need to know which anchor <a> tag to fix. Unfortunately, the evidence fie

Merge /Testing_for_Vertical_Bypassing_Authorization_Schema_WSTG-AUTHZ-00X.md into 4-Web_Application_Security_Testing/05-Authorization_Testing/03-Testing_for_Privilege_Escalation.md

Authentication via Azure/aad-pod-identity for keyvault access could be a good feature to avoid use of clientId/ clientSecret in chart values. Don't you think ?

I've found a way to bypass certain filters which implement the following behaviour: The filter checks everything between opening and closing or opening and opening brackets. A whitelist is checked against the HTML tag as well as every attribute found within the brackets. Whenever an attribute is not whitelisted the filter will block the input. Closing tags are detected as soon as a slash is found