• Injection
Cross-Site Scripting (XSS)
XSS injects attacker-controlled script into pages so it runs in victims’ browsers under your site’s origin — stealing sessions, rewriting UI, or acting as the user.
How attackers abuse it
Reflected XSS echoes input in an immediate response (search boxes, error pages). Stored XSS persists in comments, profiles, or admin panels and hits every viewer. DOM XSS abuses client-side sinks like innerHTML or unsafe URL parsing without a classic server reflection.
Attackers phish victims into clicking crafted links, or plant payloads where privileged users (support, admins) will open them — turning XSS into account takeover.
Modern SPAs still get XSS via unsanitized markdown, rich-text editors, and third-party widgets that concatenate untrusted HTML.
What proof looks like
Proof demonstrates script execution or equivalent sink control in a safe way (alert/dialog under test accounts, or a benign marker in the DOM) within scope. The finding shows the injection point, the sink, and that the origin’s privileges apply — not merely that a parameter is reflected encoded.
In PandaONE, this class maps to the Injection finding category. Alerts ship only with evidence — never as unverified scanner noise.
How to prevent it
- Encode output in context (HTML, attribute, JS, URL) and avoid building HTML from strings.
- Use framework-safe defaults; sanitize rich text with a well-maintained allowlist sanitizer.
- Deploy a strict Content-Security-Policy (nonces/hashes; minimize unsafe-inline).
- Set cookies HttpOnly and Secure; prefer short-lived tokens.
- Treat admin and support UIs as high-value XSS targets — extra scrutiny on stored fields.
• Related tools
• Glossary
• Related pages
Hunt this class with proof
Or scan your domain.