This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
OWASP Periodic Table of Vulnerabilities - Cross-Site Scripting (XSS)
Return to Periodic Table Working View
Cross-Site Scripting (XSS)
Root Cause Summary
Browser / Standards Solution
Browser vendors and standards bodies should agree on markup for elements to contain dynamic content (e.g. Flash, JavaScript, HTML, etc.) inline without allowing the dynamic content to perform malicious actions such as navigating the parent window, reading or writing data across trust boundaries, or other undesirable behaviors as determined by the owner of the containing page.
Perimeter Solution
None
Generic Framework Solution
Automatically sanitize any dynamic content before writing it into HTML, XML, or other documents that might be rendered by user agents that execute active content. If dynamic content must include dangerous elements, provide APIs which filter and sanitize potentially dangerous attributes of these elements. Exceptions and attribute configurations should be described by a policy file instead of hard-coded into the framework itself or into function calls.
Custom Framework Solution
None
Custom Code Solution
None
Discussion / Controversy
References
[https://www.owasp.org/index.php/Cross-site_Scripting_(XSS) OWASP Cross-site Scripting (XSS)
]
OWASP – XSS (Cross Site Scripting) Prevention Cheat Sheet
The Web Application Security Consortium – Cross Site Scripting