A library comment field stores script that later runs in an administrator’s browser. Which XSS class best describes that pattern?
Select an answer to reveal the explanation.
Short Explanation
The nasty part of stored XSS is the delay: plant it once, and it can fire later when an admin opens the thread. That persistence is why it often outranks a one-off reflected bounce. Comments that keep script for privileged eyes are a classic stored class.
Full Explanation
Stored (persistent) XSS saves malicious content that is later rendered to other users, including privileged operators. That persistence and privileged-victim potential commonly elevate business impact versus one-time reflected cases. The pattern is not limited to DOM-only sinks and is not harmless “CSR-only” text. Assessments should classify stored XSS distinctly and discuss who can be affected when the payload is viewed.