Skip to content
StrikeOps

Stored Cross-Site Scripting (XSS)

HighTypical severity Web applications and APIsCWE-79ATT&CK T1189

01Description

User-supplied content was stored by the application and later rendered to other users without appropriate output encoding, allowing script to be stored and executed in their browsers.

02Impact

Any user who views the affected content, potentially including administrators, runs the attacker's script in their session. This can lead to account takeover, actions performed as the victim and theft of data displayed in the application.

03Severity

Typically

High

Typically High. Usually High because the payload runs for every user who views it, including administrators. Medium if only the submitting user can see the stored content.

04How to verify

  1. 1Submit a benign script payload into fields that are displayed to other users, such as names, comments and descriptions.
  2. 2View the content as a second test user and confirm execution.
  3. 3Identify which roles view the affected content.

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

  1. 1Apply context-aware output encoding wherever stored data is rendered.
  2. 2Sanitize rich text with a maintained allow-list sanitizer.
  3. 3Deploy a strict Content Security Policy and set HttpOnly on session cookies.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo