How XSS attacks exploit unescaped output in PHP - Quick Revision & Summary

Recall & Review

beginner

What is an XSS attack?

XSS (Cross-Site Scripting) is a security attack where an attacker injects malicious scripts into web pages viewed by other users.

beginner

Why does unescaped output lead to XSS vulnerabilities?

Unescaped output allows attackers to insert harmful code that the browser runs as part of the page, because the output is not treated as plain text.

beginner

What does 'escaping output' mean in PHP?

Escaping output means converting special characters like <, >, & into safe codes so browsers show them as text, not code.

intermediate

Show a simple PHP example where unescaped output causes XSS.

If you do:
<?php echo $_GET['name']; ?>
and someone visits ?name=<script>alert('XSS')</script>, the script runs.

beginner

How to fix XSS vulnerabilities in PHP output?

Use functions like htmlspecialchars() to escape output before showing it on the page.

What does XSS stand for?

A Cross-Site Scripting

B Cross-Site Sharing

C Cross-Site Security

D Cross-Site Storage

XSS means Cross-Site Scripting, a type of security attack.

Why is unescaped output dangerous in PHP?

A It can allow attackers to run harmful scripts in users' browsers

B It makes the page load slower

C It causes syntax errors in PHP

D It hides errors from the developer

Unescaped output lets attackers inject scripts that run in users' browsers.

Which PHP function helps prevent XSS by escaping output?

A strtoupper()

B strip_tags()

C trim()

D htmlspecialchars()

htmlspecialchars() converts special characters to safe HTML entities.

What happens if you output user input directly without escaping?

A The server crashes

B Malicious code can run in the browser

C The page becomes invisible

D Nothing happens

Direct output without escaping can let attackers run harmful scripts.

Which character should be escaped to prevent XSS?

A 1

B a

C <

D z

The < character starts HTML tags and must be escaped to prevent code injection.

Explain how unescaped output in PHP can lead to an XSS attack.

Think about what happens when user input is shown directly on a page.

Describe how to prevent XSS attacks when displaying user input in PHP.

Focus on the function that changes < and > to safe codes.

Practice

1. What is the main reason XSS attacks happen in PHP applications?

easy

A. Using too many PHP functions

B. PHP code has syntax errors

C. User input is displayed without escaping special characters

D. Database connection fails

Solution

1. Step 1: Understand XSS attack cause

   XSS attacks exploit when user input is shown directly in HTML without cleaning.

2. Step 2: Identify the vulnerability

   Displaying user input without escaping special characters allows malicious scripts to run.

3. Final Answer:

   User input is displayed without escaping special characters -> Option C

4. Quick Check:

   XSS = unescaped user input [OK]

Hint: XSS = unsafe output from user input [OK]

Common Mistakes:

• Thinking syntax errors cause XSS
• Confusing database errors with XSS
• Believing PHP functions cause XSS

2. Which PHP function is commonly used to prevent XSS by escaping output?

easy

A. json_encode()

B. strtoupper()

C. array_merge()

D. htmlspecialchars()

Solution

1. Step 1: Identify escaping function

   htmlspecialchars() converts special characters to HTML entities, preventing script execution.

2. Step 2: Compare other functions

   strtoupper() changes case, array_merge() combines arrays, json_encode() formats JSON, none escape HTML.

3. Final Answer:

   htmlspecialchars() -> Option D

4. Quick Check:

   Escape HTML = htmlspecialchars() [OK]

Hint: Escape HTML output with htmlspecialchars() [OK]

Common Mistakes:

• Using strtoupper() to escape HTML
• Confusing json_encode() with escaping HTML
• Not escaping output at all

3. What will be the output of this PHP code?

<?php
$user_input = '<script>alert("XSS")</script>';
echo $user_input;
?>

medium

A. An error message

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

C. alert("XSS")

D. &lt;script&gt;alert("XSS")&lt;/script&gt;

Solution

1. Step 1: Analyze echo without escaping

   Echo prints the string as is, so HTML tags appear literally and run as code in browser.

2. Step 2: Understand output effect

   The output is the raw script tag, so browser will execute alert("XSS").

3. Final Answer:

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

4. Quick Check:

   Unescaped output = raw script tag [OK]

Hint: Echo raw input shows script tags as is [OK]

Common Mistakes:

• Thinking output is escaped automatically
• Expecting an error message
• Confusing escaped output with raw output

4. Identify the error in this PHP snippet that leads to XSS vulnerability:

<?php
$name = $_GET['name'];
echo "<p>Hello, $name</p>";
?>

medium

A. Missing htmlspecialchars() to escape $name before echo

B. Using double quotes instead of single quotes

C. Not checking if $_GET['name'] is set

D. Echo statement syntax is incorrect

Solution

1. Step 1: Check output handling of user input

   $name is output directly inside HTML without escaping special characters.

2. Step 2: Identify missing security step

   htmlspecialchars() is needed to prevent scripts in $name from running.

3. Final Answer:

   Missing htmlspecialchars() to escape $name before echo -> Option A

4. Quick Check:

   Escape user input before output [OK]

Hint: Always escape variables before echoing HTML [OK]

Common Mistakes:

• Thinking quotes cause XSS
• Ignoring need to escape user input
• Assuming isset check prevents XSS

5. You want to safely display user comments stored in $comment on a webpage. Which code snippet best prevents XSS attacks?

hard

A. <?php echo htmlspecialchars($comment, ENT_QUOTES | ENT_HTML5); ?>

B. <?php echo strip_tags($comment); ?>

C. <?php echo nl2br($comment); ?>

D. <?php echo $comment; ?>

Solution

1. Step 1: Understand escaping user comments

   htmlspecialchars() converts special characters to safe HTML entities, preventing scripts.

2. Step 2: Compare other options

   strip_tags() removes tags but can remove valid content; nl2br() adds line breaks but no escaping; echo raw outputs unsafe.

3. Final Answer:

   <?php echo htmlspecialchars($comment, ENT_QUOTES | ENT_HTML5); ?> -> Option A

4. Quick Check:

   Escape all special chars with htmlspecialchars() [OK]

Hint: Use htmlspecialchars() with ENT_QUOTES for full escaping [OK]

Common Mistakes:

• Relying on strip_tags() alone
• Not escaping quotes in output
• Outputting raw user input