XSS by changing path
Testing vulnerability by injecting malicious scripts in filenames to bypass security measures and execute unauthorized code.
Cross-site scripting (XSS)
How this template works
APIs Selection
The API selection filters in this template specify the criteria for selecting the APIs to be tested. In this case, the filters include checking the response code to be between 200 and 300, and the response payload to contain the HTML doctype declaration "<!doctype html>".
Execute request
The execute section of the template defines the actions to be performed during the request execution. It includes modifying the URL by removing the trailing slash and injecting a malicious script into the path. The modified URL is then used to send the request.
Validation
The validation section specifies the expected response from the API. It checks if the response payload contains either the script tag "<script>alert(document.domain)</script>" or the HTML doctype declaration "<!doctype html>". If either of these is present in the response, it indicates a potential XSS vulnerability.
Frequently asked questions
What is the purpose of the XSS_IN_PATH test
What is the impact of an XSS vulnerability
What category and subcategory does the XSS_IN_PATH test belong to
What are the severity and tags associated with the XSS_IN_PATH test
What are the API selection filters used in this test
How does the test modify the URL and what is the validation criteria
"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "
Security team,
Rippling
