Request To Response Tainted Input
Untrusted request input is written into the HTTP response (or marked as raw HTML) without output encoding, enabling reflected cross-site scripting (CWE-79).
Standards mapping
- OWASP Top 10
- A03:2021 - Injection
- OWASP ASVS
- V5.3.3 (L1)
Vulnerable vs. safe
Response.Write(q);Response.Write(HttpUtility.HtmlEncode(q));Why it matters & how to fix it
Untrusted request input is written into the HTTP response (or marked as raw HTML) without output encoding, enabling reflected cross-site scripting (CWE-79). HTML-encode the value with HttpUtility.HtmlEncode / WebUtility.HtmlEncode, or render it through a Razor view where '@model' output is contextually auto-escaped; never use Html.Raw on user data.
References
Rule ID integsec.csharp.xss.request-to-response-taint - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Cross-Site Scripting (XSS)DOM XSS Innerhtml Sink
- JavaScript / TypeScript - Cross-Site Scripting (XSS)Reflected XSS Response Tainted Input
- JavaScript / TypeScript - Cross-Site Scripting (XSS)React Dangerously Set Inner HTML
- Go - Cross-Site Scripting (XSS)Text Template For HTML
- Go - Cross-Site Scripting (XSS)XSS Response Write
- Go - Cross-Site Scripting (XSS)XSS Template HTML Bypass