01Description
User-supplied input was reflected in the application's response without appropriate output encoding, allowing script to be injected and executed in the browser of a user who opens a crafted link.
02Impact
An attacker who persuades a user to open a crafted link can run script in the user's session, allowing actions to be performed as the user, data on the page to be read, or a fake login form to be displayed.
03Severity
Typically
Medium
Typically Medium. Usually Medium. High if it affects an authenticated area with privileged users, session cookies are readable by script, or it is stored rather than reflected.
04How to verify
- 1Identify parameters reflected in responses.
- 2Test with harmless payloads to confirm script execution, noting the context (HTML, attribute, JavaScript).
- 3Record the affected parameter, page and a proof-of-concept URL using a benign payload.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Apply context-aware output encoding to all user-supplied data, using the framework's auto-escaping.
- 2Avoid inserting untrusted data into script blocks or event handlers.
- 3Deploy a strict Content Security Policy as defense in depth.
- 4Set HttpOnly on session cookies.
06References
Draft findings like this from your own evidence
Book a demo