Cross-Site Scripting (Generic)

This bucket holds XSS reports that triagers didn't categorize as reflected, stored, or DOM-based. The patterns are a superset of those specific subcategories: any input field, header, cookie, or referenced URL that lands in the DOM unsanitized. Most reports filed under this generic label could, on closer inspection, be reclassified as reflected (a path or URL parameter) or stored (a profile or comment field) once the exact injection point is identified.

• All targets from reflected/stored/DOM XSS
• Error pages reflecting headers / cookies
• Sibling-subdomain cookie scope used to seed payloads

• All vectors from reflected, stored, and DOM XSS syntheses apply
• Cookie poisoning + XSS (set attacker-controlled cookie via response splitting / sibling subdomain, then payload reflects)
• Header reflection (Referer, X-Forwarded-Host) on error pages

• <svg/onload=alert(1)>
• <img src=x onerror=alert(1)>
• javascript:alert(1)
• Cookie: foo=<svg/onload=alert(1)>
• Referer: https://attacker/<svg/onload=alert(1)>

The same testing approach used for reflected, stored, and DOM-based XSS applies here, since a "generic" report is really just one of those three patterns that hasn't been categorized yet. Worth adding on top: a cookie-reflection probe that sets a per-target cookie with a unique marker value and checks whether it comes back reflected on later responses without encoding.

Tip: Testing tools that run these checks in parallel across every discovered endpoint can cut the time required substantially compared to fully manual testing, as long as they confirm findings with more than one signal to keep the false-positive rate down.

• Same as the reflected/stored/DOM syntheses.
• Cookie-reflection probe should require both reflection AND a context that allows execution.

Manual Testing Methodology

Here is a systematic approach to identifying Cross-Site Scripting (Generic) vulnerabilities in a target application.

Before testing, map all input vectors that could be affected. Identify parameters, headers, cookies, and request bodies that interact with the vulnerable component. A proxy such as Burp Suite or OWASP ZAP, paired with normal browsing of the target, is usually enough to build this list.

Send a legitimate request and record the normal response: status code, content length, response time, and any identifying tokens. This baseline matters because it's what you'll compare later responses against once payloads are involved.

Inject test payloads into each identified input vector one at a time. Start with benign detection payloads before escalating to anything that could actually trigger the vulnerability. For Cross-Site Scripting (Generic) specifically, inject a unique, easily-searchable marker string into every parameter first to map which ones reflect at all, then follow up on the reflecting ones with context-appropriate breakout payloads — "><svg/onload= for an HTML/attribute context, ';alert(1);// for a JavaScript string context, javascript: for a URL context.

Compare the response against your baseline, looking specifically for whether the marker or payload comes back unencoded and in an executable position — a reflected < that renders as < in the page source is evidence of correct encoding, not a finding, no matter how the marker itself looks in a diff.

Once a potential vulnerability is detected, confirm it with at least a few independent test cases to rule out coincidence. Document the exact request and response as proof. For Cross-Site Scripting (Generic), a confirmed finding typically means showing that attacker-controlled input changes the application's behavior in a way that matters for security, not just that a payload was reflected somewhere harmless.

Real-World Impact

Cross-site scripting lets attackers execute arbitrary JavaScript in a victim's browser, effectively hijacking their authenticated session. This leads to session token theft, credential harvesting through fake login forms, cryptocurrency mining in the browser, defacement, and in social platforms, worm-like propagation from one infected profile to the next.

Stored XSS is particularly severe because it can affect every user who views the poisoned content, meaning a single injection point can compromise thousands of sessions at once. It's also frequently chained with CSRF to perform administrative actions or exfiltrate internal data once an attacker has script execution in an authenticated context.

XSS remains one of the most commonly reported vulnerability classes across web applications of every size, which is part of why it still shows up so often in disclosed reports despite being well understood.

Prevention and Secure Coding

Preventing Cross-Site Scripting (Generic) takes a defense-in-depth approach — no single control below is sufficient alone, but together they close off both the primary path and the most common bypasses.

Context-aware output encoding. Encode output for the exact context it lands in — HTML body, HTML attribute, JavaScript string, or URL — at render time, not once globally; the same value needs different encoding depending on where it's placed.

Auto-escaping frameworks. Modern templating and component frameworks (React, Vue, Angular) escape output by default — the actual risk concentrates in the explicit escape hatches (dangerouslySetInnerHTML, v-html, [innerHTML]) that bypass that protection, so audit those call sites specifically.

Content-Security-Policy. A script-src CSP built on nonces or hashes (not unsafe-inline) stops injected inline scripts from executing even if a payload gets through the encoding layer.

Allowlist sanitization for rich text. Where users are meant to submit formatted content, sanitize it server-side with an allowlist HTML sanitizer, not a denylist regex — denylists are reliably bypassable.

Cookie flags as a backstop. HttpOnly on session cookies limits the blast radius of a successful injection by keeping the token out of reach of document.cookie even if script execution succeeds.