Cross-site scripting (XSS) in Cybersecurity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Cross-site scripting (XSS)?

Cross-site scripting (XSS) is a security vulnerability where attackers inject malicious scripts into trusted websites. These scripts run in users' browsers, potentially stealing data or performing harmful actions.

intermediate

Name the three main types of XSS attacks.

The three main types of XSS are:
1. Stored XSS: Malicious code is saved on the website's server.
2. Reflected XSS: Malicious code is reflected off a web server, like in a URL.
3. DOM-based XSS: The attack happens in the browser by manipulating the page's Document Object Model.

beginner

Why is XSS dangerous for users?

XSS is dangerous because it can steal sensitive information like cookies, session tokens, or personal data. It can also trick users into actions like clicking fake links or submitting forms without their knowledge.

intermediate

How can developers prevent XSS attacks?

Developers can prevent XSS by:
1. Validating and sanitizing user input.
2. Encoding output to safely display data.
3. Using security headers like Content Security Policy (CSP).
4. Avoiding unsafe JavaScript functions that insert HTML directly.

intermediate

What role does Content Security Policy (CSP) play in XSS protection?

Content Security Policy (CSP) is a security feature that restricts which scripts can run on a webpage. It helps block malicious scripts injected by attackers, reducing the risk of XSS attacks.

Which type of XSS stores malicious code on the website's server?

A SQL Injection

B Reflected XSS

C DOM-based XSS

D Stored XSS

Stored XSS saves the malicious script on the server, so it runs whenever a user accesses the infected page.

What is a common goal of an XSS attack?

A Increase website speed

B Steal user cookies

C Improve SEO ranking

D Backup website data

Attackers often use XSS to steal cookies, which can give them access to user accounts.

Which method helps prevent XSS by restricting allowed scripts on a webpage?

A Content Security Policy (CSP)

B Firewall

C Antivirus software

D Password encryption

CSP controls which scripts can run, blocking unauthorized or malicious scripts.

Reflected XSS attacks usually happen through:

A User input reflected in URLs or forms

B Malicious code saved in the database

C Manipulating browser extensions

D Physical access to the server

Reflected XSS occurs when malicious input is immediately reflected back in a webpage, often via URLs or form inputs.

Which practice is NOT effective against XSS?

A Sanitizing user input

B Encoding output

C Using strong passwords

D Implementing CSP

Strong passwords protect accounts but do not prevent XSS attacks directly.

Explain what Cross-site scripting (XSS) is and why it is a security risk.

Think about how attackers use websites to run harmful code in your browser.

Describe three main types of XSS attacks and how they differ.

Consider where the bad script is saved or how it reaches the user.

Practice

1. What is the main risk of a Cross-site Scripting (XSS) attack?

easy

A. Attackers physically damage the website server

B. Attackers change the website's design without permission

C. Attackers block access to the website by flooding it with traffic

D. Attackers run harmful scripts on a website to steal user data

Solution

1. Step 1: Understand what XSS does

   XSS allows attackers to inject harmful scripts into websites that run on users' browsers.

2. Step 2: Identify the main risk

   These harmful scripts can steal sensitive user data like passwords or cookies.

3. Final Answer:

   Attackers run harmful scripts on a website to steal user data -> Option D

4. Quick Check:

   XSS risk = harmful scripts stealing data [OK]

Hint: XSS = bad scripts stealing user info on websites [OK]

Common Mistakes:

• Confusing XSS with server damage
• Thinking XSS blocks website access
• Believing XSS changes website design only

2. Which of the following is a correct way to prevent XSS in web code?

easy

A. Allow all user input without filtering

B. Use only images and no text on the website

C. Escape special characters like < and > before displaying user input

D. Disable the website's login page

Solution

1. Step 1: Identify safe coding practice

   Escaping special characters like < and > stops harmful scripts from running as code.

2. Step 2: Check other options

   Allowing all input is unsafe, disabling login or using only images does not prevent XSS.

3. Final Answer:

   Escape special characters like < and > before displaying user input -> Option C

4. Quick Check:

   Escape input = prevent XSS [OK]

Hint: Escape < and > in input to stop scripts [OK]

Common Mistakes:

• Allowing all input without checks
• Thinking disabling login stops XSS
• Believing images-only stops script attacks

3. Consider this HTML snippet showing user input:

<div>User comment: <script>alert('XSS')</script></div>

What will happen if the website does NOT sanitize this input?

medium

A. The alert box with message 'XSS' will appear to the user

B. The script tags will be shown as plain text

C. The website will crash immediately

D. Nothing will happen; input is safe

Solution

1. Step 1: Understand unsanitized script tags

   If input is not cleaned, the <script> tag runs as code in the browser.

2. Step 2: Predict the effect

   The alert('XSS') script runs, showing a popup alert with 'XSS'.

3. Final Answer:

   The alert box with message 'XSS' will appear to the user -> Option A

4. Quick Check:

   Unsanitized script runs alert [OK]

Hint: Unsanitized <script> runs code, shows alert [OK]

Common Mistakes:

• Thinking script tags show as text without sanitizing
• Assuming website crashes from script
• Believing nothing happens without sanitizing

4. A developer wrote this code to display user input safely:

output = user_input.replace("<", "<").replace(">", ">")

But users still report XSS attacks. What is the likely problem?

medium

A. The code only replaces < and > but misses other dangerous characters

B. The code should remove all user input instead of replacing

C. The code runs on the server, but XSS happens on the client

D. The code is perfect; users are mistaken

Solution

1. Step 1: Analyze the replacement method

   Replacing only < and > misses other characters like quotes or script event handlers that can cause XSS.

2. Step 2: Understand XSS complexity

   Effective XSS prevention requires comprehensive escaping or using security libraries, not just partial replacements.

3. Final Answer:

   The code only replaces < and > but misses other dangerous characters -> Option A

4. Quick Check:

   Partial escaping misses XSS vectors [OK]

Hint: Partial escaping misses XSS; escape all special chars [OK]

Common Mistakes:

• Thinking removing input is only solution
• Confusing server vs client execution
• Believing partial replacement is enough

5. A website allows users to post comments that include HTML. To prevent XSS, which combined approach is best?

hard

A. Allow all HTML tags but filter out <script> tags only

B. Use a whitelist to allow only safe HTML tags and escape the rest

C. Escape all user input so no HTML tags run as code

D. Disable comments feature entirely to avoid XSS

Solution

1. Step 1: Understand risks of allowing HTML

   Allowing all HTML except script tags is risky because other tags or attributes can cause XSS.

2. Step 2: Identify best practice

   Using a whitelist to allow only safe tags and escaping others balances usability and security.

3. Step 3: Evaluate other options

   Escaping all input removes HTML functionality; disabling comments reduces user engagement.

4. Final Answer:

   Use a whitelist to allow only safe HTML tags and escape the rest -> Option B

5. Quick Check:

   Whitelist safe tags + escape others = best XSS defense [OK]

Hint: Whitelist safe HTML tags, escape others to stop XSS [OK]

Common Mistakes:

• Allowing all HTML except scripts
• Escaping all input losing HTML features
• Disabling comments instead of fixing XSS