XSS testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does XSS stand for in web security?

XSS stands for Cross-Site Scripting. It is a security vulnerability where attackers inject malicious scripts into trusted websites.

beginner

Why is XSS testing important?

XSS testing helps find security holes where attackers can run harmful scripts on users' browsers, protecting users and data.

intermediate

Name two common types of XSS attacks.

The two common types are Stored XSS (where malicious code is saved on the server) and Reflected XSS (where malicious code is reflected off a web server).

beginner

What is a simple test input to check for XSS vulnerability?

A simple test input is: . If this runs as a popup, the site is vulnerable.

intermediate

How can developers prevent XSS attacks?

Developers can prevent XSS by validating and encoding user inputs, using security headers, and applying Content Security Policy (CSP).

What does XSS testing primarily check for?

A Broken links on a website

B Slow page loading times

C Injection of malicious scripts into web pages

D Incorrect spelling on web pages

XSS testing checks if malicious scripts can be injected and run on web pages.

Which of these is a common sign of an XSS vulnerability?

A Page has a sitemap

B User input is displayed without filtering

C Website uses HTTPS

D Page images do not load

Displaying user input without filtering can allow malicious scripts to run, causing XSS.

Stored XSS differs from Reflected XSS because Stored XSS:

A Does not involve scripts

B Only affects the browser cache

C Is always harmless

D Saves malicious code on the server

Stored XSS saves the malicious script on the server, affecting multiple users.

Which method helps prevent XSS attacks?

A Encoding user inputs before display

B Disabling JavaScript completely

C Using large images

D Increasing server RAM

Encoding user inputs stops malicious scripts from running by treating them as text.

A simple test script to check for XSS is:

A <script>alert('XSS')</script>

B <img src='image.jpg'>

C <div>Hello</div>

D <a href='link'>Click</a>

This script triggers an alert if XSS is possible.

Explain what XSS testing is and why it matters for website security.

Think about how attackers use scripts and what harm they cause.

Describe two types of XSS attacks and how you might test for them.

Consider where the malicious code is stored or reflected.

Practice

1. What is the main goal of XSS testing in software testing?

easy

A. To check if harmful scripts can run on a website

B. To test website speed under heavy load

C. To verify database backup integrity

D. To check user interface responsiveness

Solution

1. Step 1: Understand XSS testing purpose

   XSS testing aims to find if malicious scripts can run on a website, which can harm users or data.

2. Step 2: Compare options to XSS goal

   Only "To check if harmful scripts can run on a website" matches the goal of detecting harmful script execution on websites.

3. Final Answer:

   To check if harmful scripts can run on a website -> Option A

4. Quick Check:

   XSS testing = harmful script check [OK]

Hint: XSS testing checks for harmful scripts running on sites [OK]

Common Mistakes:

• Confusing XSS testing with performance testing
• Thinking XSS tests database or UI only
• Ignoring script execution risks

2. Which of the following is a correct example of an XSS test input to check script injection?

easy

A. SELECT * FROM users;

B. <script>alert('XSS')</script>

C. DROP TABLE users;

D. console.log('test')

Solution

1. Step 1: Identify typical XSS test input

   XSS tests use script tags like <script>alert('XSS')</script> to check if scripts run on the site.

2. Step 2: Eliminate unrelated inputs

   Options B and C are SQL commands, not XSS scripts. console.log('test') is JavaScript code but not wrapped in script tags for injection.

3. Final Answer:

   <script>alert('XSS')</script> -> Option B

4. Quick Check:

   Script tags = XSS test input [OK]

Hint: XSS test inputs use <script> tags to inject scripts [OK]

Common Mistakes:

• Using SQL commands as XSS inputs
• Not wrapping JavaScript in script tags
• Confusing console logs with injection

3. Given this input in a web form: <img src=x onerror=alert('XSS')>, what is the expected result if the site is vulnerable to XSS?

medium

A. The image will load normally without alert

B. The input will be saved as plain text without alert

C. The form submission will fail with an error

D. The alert box with message 'XSS' will appear

Solution

1. Step 1: Understand the input behavior

   The input uses an image tag with an invalid source and an onerror event that triggers an alert. If the site is vulnerable, this script runs.

2. Step 2: Predict the output on vulnerability

   If vulnerable, the alert('XSS') will execute, showing a popup message.

3. Final Answer:

   The alert box with message 'XSS' will appear -> Option D

4. Quick Check:

   onerror alert triggers popup if vulnerable [OK]

Hint: onerror event triggers alert if XSS vulnerability exists [OK]

Common Mistakes:

• Assuming input is saved as text without execution
• Thinking image loads normally despite invalid src
• Confusing form errors with script execution

4. You wrote this test input to check XSS: <script>alert('test')</script>. The alert does not appear, but the input is stored and shown as text on the page. What is the likely reason?

medium

A. The site properly escapes script tags to prevent execution

B. The browser blocked all JavaScript on the page

C. The input was rejected and not saved

D. The alert function is disabled in the browser

Solution

1. Step 1: Analyze why alert did not appear

   The alert script is stored and shown as text, meaning it was not executed but escaped.

2. Step 2: Identify cause of script escaping

   Proper XSS protection escapes script tags so they display as text, preventing execution.

3. Final Answer:

   The site properly escapes script tags to prevent execution -> Option A

4. Quick Check:

   Escaping scripts = no execution [OK]

Hint: Escaping script tags stops alert from running [OK]

Common Mistakes:

• Assuming browser blocked all JavaScript
• Thinking input was rejected when it was saved
• Believing alert function is disabled

5. You want to test if a website properly blocks XSS attacks in both URL parameters and form inputs. Which combined approach is best?

hard

A. Test URL parameters with SQL commands and form inputs with numbers

B. Only test form inputs with normal text values

C. Inject <script>alert(1)</script> in URL and form fields, then check if alert appears

D. Use browser developer tools to disable JavaScript and test inputs

Solution

1. Step 1: Understand testing both input types

   XSS can happen via URL parameters or form inputs, so both must be tested with script injections.

2. Step 2: Choose effective test input and verification

   Injecting <script>alert(1)</script> is a simple way to check if scripts run. Observing alert confirms vulnerability.

3. Final Answer:

   Inject <script>alert(1)</script> in URL and form fields, then check if alert appears -> Option C

4. Quick Check:

   Test scripts in URL and forms to find XSS [OK]

Hint: Test script injection in both URL and forms for full coverage [OK]

Common Mistakes:

• Testing only one input type
• Using unrelated inputs like SQL commands
• Disabling JavaScript instead of testing execution