XSS
XSS (cross-site scripting) is a common web security vulnerability in which an attacker injects malicious scripts into a web page. When other users browse that page, the script executes, allowing the attacker to steal user information or perform other malicious operations.
Core Facts
Timeline (last 90 days)
XSS (Cross-Site Scripting) is when a page renders user input directly as HTML, causing malicious scripts to execute in other people's browsers; it is divided into reflected, stored, and DOM types.
HttpOnly cookies can prevent JavaScript from reading session tokens, and are an effective measure against XSS session theft.
The CSP response header, by restricting script source domains and inline script execution, can prevent malicious code from running when XSS injection occurs, and is the second line of defense for React applications.
Using dangerouslySetInnerHTML in React bypasses the automatic escaping mechanism, leaving the developer fully responsible for content sanitization, and it is a common entry point for XSS.
React's JSX rendering automatically escapes strings before inserting them into the DOM, thereby eliminating most traditional XSS attack paths.
If the refresh token is placed in localStorage, an XSS occurrence is equivalent to account compromise.
If LLM output is rendered or executed without encoding, it can lead to XSS (when rendered as HTML/Markdown), SQL injection (when concatenated into database queries), and SSRF (when URLs are included for backend fetching).
Blindly injecting large numbers of payloads will trigger WAFs and cause the IP to be blocked, making it impossible to detect vulnerabilities even if they exist in the target.
A good XSS detection Skill should adopt a layered process of reconnaissance before escalation: first check whether the Content-Type is text/html, test reflection with a unique marker, inject HTML first to determine HTML injection, and then escalate step by step to XSS.
Tokens stored in localStorage can persist after a tab is closed, but are exposed to XSS risks
7 more timeline events
All Facts (18)
Vulnerabilities such as SQL injection, XSS, and SSRF have long occupied the OWASP Top 10 security risk list.
75%UnverifiedXSS (Cross-Site Scripting) is when a page renders user input directly as HTML, causing malicious scripts to execute in other people's browsers; it is divided into reflected, stored, and DOM types.
50%UnverifiedHttpOnly cookies can prevent JavaScript from reading session tokens, and are an effective measure against XSS session theft.
50%UnverifiedReact's JSX rendering automatically escapes strings before inserting them into the DOM, thereby eliminating most traditional XSS attack paths.
50%UnverifiedUsing dangerouslySetInnerHTML in React bypasses the automatic escaping mechanism, leaving the developer fully responsible for content sanitization, and it is a common entry point for XSS.
50%UnverifiedThe CSP response header, by restricting script source domains and inline script execution, can prevent malicious code from running when XSS injection occurs, and is the second line of defense for React applications.
50%UnverifiedIf the refresh token is placed in localStorage, an XSS occurrence is equivalent to account compromise.
50%UnverifiedIf LLM output is rendered or executed without encoding, it can lead to XSS (when rendered as HTML/Markdown), SQL injection (when concatenated into database queries), and SSRF (when URLs are included for backend fetching).
50%UnverifiedBlindly injecting large numbers of payloads will trigger WAFs and cause the IP to be blocked, making it impossible to detect vulnerabilities even if they exist in the target.
50%UnverifiedA good XSS detection Skill should adopt a layered process of reconnaissance before escalation: first check whether the Content-Type is text/html, test reflection with a unique marker, inject HTML first to determine HTML injection, and then escalate step by step to XSS.
50%UnverifiedTokens stored in memory are lost after a page refresh, but are more secure because XSS attacks cannot read them via document.cookie or localStorage
50%UnverifiedTokens stored in localStorage can persist after a tab is closed, but are exposed to XSS risks
50%UnverifiedStoring JWT in HTTP-only cookies prevents client-side JavaScript from reading the token, thereby defending against XSS attacks that steal authentication credentials.
50%UnverifiedPattern-based vulnerabilities such as SQL injection and XSS have clear characteristics and relatively standardized remediation approaches that AI models can learn through training data.
50%UnverifiedCommon types of focused web vulnerability training include SQL injection, XSS, privilege escalation vulnerabilities, and front-end JS code auditing.
50%UnverifiedCSP (Content Security Policy) is an HTTP security header that defends against cross-site scripting (XSS) and data injection attacks through a whitelist mechanism.
50%UnverifiedSync-in 2.5 fixes a stored XSS vulnerability in SVG thumbnail processing.
50%UnverifiedSync-in 2.5 fixes SVG thumbnail processing and stored XSS vulnerabilities.
50%