> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Check whether user-supplied comments, profiles, or other shared content can execute in another user’s browser.

# Cross-site scripting (XSS) testing for web applications


[← Back to attack scenarios](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios)

Cross-site scripting (XSS) happens when a web page treats untrusted content as code. This scenario focuses on what happens in another user's browser when an application displays user-supplied material.

Comments, profile fields, and shared documents are examples of content other users can see. Stored XSS can affect later visitors. It happens when an app saves user content and then renders it as executable code.

A finding identifies the affected page or feature and the browser execution observed there. For a separate assessment of code the site deliberately loads from vendors, see [OPTIMJACK and third-party JavaScript](https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/optimjack).

The app lists this scenario as **Execute attacker-controlled content in another user's browser** (`APP-12`) in [Application Red Teaming](https://www.superagent.sh/docs/products/red-teaming/applications).

## Standards and guidance

[CWE-79 Cross-Site Scripting (XSS)](https://cwe.mitre.org/data/definitions/79.html)

---
Source: https://www.superagent.sh/docs/products/red-teaming/attack-scenarios/application-browser-content-isolation
Index: https://www.superagent.sh/llms.txt
