Rule Definition
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it. An attacker can use XSS to send a malicious script to an unsuspecting user. The end user’s browser has no way to know that the script should not be trusted, and will execute the script. Because it thinks the script came from a trusted source, the malicious script can access any cookies, session tokens, or other sensitive information retained by the browser and used with that site. These scripts can even rewrite the content of the HTML page. For more details on the different types of XSS flaws, see: Types of Cross-Site Scripting. Request Validation is a feature that prevents potentially dangerous content from being submitted. This feature is enabled by default. However, at times you might need your application to post HTML markup tags to the server. You would then need this feature to be disabled.

Remediation
Ensure the validation request is always enabled when using HttpPost/HttpPut (or equivalent) requests

Violation Code Sample

[ValidateInput(false)]
 public class HomeController : Controller
 {
 }

Fixed Code Sample

[ValidateInput(true)]
 public class HomeController : Controller
 {
 }

https://docs.microsoft.com/en-us/aspnet/whitepapers/request-validation https://www.owasp.org/index.php/Top_10-2017_A7-Cross-Site_Scripting_(XSS)