CyberKit

Cross-Site Scripting

Also called XSS.

Injecting attacker script that runs in other users' browsers.

What it is

A web vulnerability where untrusted input is reflected into a page without proper encoding, causing the victim's browser to execute attacker-controlled script in the site's origin. It comes in stored, reflected, and DOM-based forms.

Why it matters

XSS lets attackers steal sessions, perform actions as the victim, and harvest data, and it sits on the OWASP Top 10; investigations look for the injection point, the payload, and what it exfiltrated.

In practice

A comment field that stores '<script>' so every visitor's session cookie is sent to the attacker.

What to look for

  • Script tags or event handlers in parameters.
  • User content rendered without encoding.
  • CSP violation reports.

Common mistake

Filtering a few tags. Encode output for its context and add a strict CSP.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources