Glossary
XSS
Definition
Cross-site scripting (XSS) lets attacker-controlled code run in someone's browser through a website they use.
The browser may treat the malicious code as part of the website. HTTPS protects transport but does not make all page content safe.
A customer may include “XSS” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Cross-site scripting (XSS) is a website weakness that allows attacker-controlled code to execute in another person's browser. The code is delivered through a site the person visits, so the browser may treat it as belonging to that site.
The unsafe content might be stored in a comment or profile and shown later, reflected from a request, or produced by the page's own handling of data. Depending on the weakness and browser protections, it can alter what the person sees or perform actions in their session. It does not always mean the website's server has been taken over.
Hypothetical example: a small software company's support dashboard displays a customer's submitted text as active page content. A malicious submission runs code when a support agent opens the ticket. The dashboard's use of HTTPS does not prevent that application flaw.
Developers need context-appropriate output encoding and safe handling of any intentionally allowed HTML. Content security policies can provide additional defence, but should not replace fixing unsafe code. Encode output for its context and handle intentionally allowed HTML safely. Test every place user-supplied content appears; a content security policy adds a layer but does not replace fixing unsafe rendering. A generic claim that all input is filtered does not explain whether each output context is safe.
Sources: OWASP cross-site scripting overview; OWASP XSS prevention guidance.