XSS prevention in templates in Vue - Performance & Optimization

Performance: XSS prevention in templates

HIGH IMPACT

This affects page security and rendering speed by controlling how user input is handled and displayed in templates.

Displaying user-generated content safely in Vue templates

Vue

<template>
  <div>{{ userInput }}</div>
</template>
<script setup>
const userInput = '<img src=x onerror=alert(1)>'
</script>

Vue automatically escapes HTML in mustache syntax, preventing script execution and avoiding layout shifts.

📈 Performance GainNo extra reflows or layout shifts caused by injected scripts; safer and more stable rendering.

Displaying user-generated content safely in Vue templates

Vue

<template>
  <div v-html="userInput"></div>
</template>
<script setup>
const userInput = '<img src=x onerror=alert(1)>'
</script>

Using v-html directly with untrusted input allows malicious scripts to run, causing security risks and potential layout shifts.

📉 Performance CostTriggers layout shifts (CLS) and can block interaction (INP) if scripts execute unexpectedly.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Using v-html with untrusted input	Adds nodes dynamically	Triggers multiple reflows if scripts modify layout	High due to repaints and possible script execution	[X] Bad
Using {{ }} interpolation for user input	No extra nodes, text only	No reflows caused by script injection	Low paint cost, stable layout	[OK] Good

Rendering Pipeline

Vue escapes user input during template compilation, so the browser renders text safely without executing scripts. This avoids extra layout recalculations caused by dynamic HTML injection.

→Template Compilation

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout and Paint stages can be expensive if malicious HTML causes reflows or repaints.

Core Web Vital Affected

INP

This affects page security and rendering speed by controlling how user input is handled and displayed in templates.

Optimization Tips

1Always use {{ }} interpolation for user content to prevent XSS.

2Avoid v-html with untrusted data to prevent layout shifts and script execution.

3Check DevTools for unexpected DOM changes and layout shifts after rendering user input.

Performance Quiz - 3 Questions

Which Vue template syntax prevents XSS by escaping user input?

A Directly setting innerHTML in mounted hook

B Using {{ userInput }} interpolation

C Using v-html directive with userInput

D Using raw HTML strings in template

DevTools: Elements and Performance panels

How to check: Inspect the DOM in Elements panel to see if user input is rendered as text or HTML. Use Performance panel to record and check for layout shifts or long tasks caused by script execution.

What to look for: Look for unexpected DOM nodes or layout shifts in the flame chart indicating unsafe HTML rendering.

Practice

1. In Vue templates, which syntax automatically escapes content to prevent XSS attacks?

easy

A. Directly manipulating the DOM with JavaScript

B. Using v-html directive to insert HTML

C. Using triple curly braces like {{{ userInput }}}

D. Using double curly braces like {{ userInput }}

Solution

1. Step 1: Understand Vue's default escaping

   Vue automatically escapes content inside {{ }} to prevent XSS by converting special characters to safe HTML entities.

2. Step 2: Compare with other methods

   Using v-html inserts raw HTML and can cause XSS if content is unsafe. Direct DOM manipulation bypasses Vue's protections.

3. Final Answer:

   Using double curly braces like {{ userInput }} -> Option D

4. Quick Check:

   Vue escapes {{ }} content = A [OK]

Hint: Remember: {{ }} escapes content, v-html does not [OK]

Common Mistakes:

• Thinking v-html escapes content automatically
• Assuming v-text sanitizes HTML
• Believing direct DOM manipulation is safe

2. Which of the following Vue template usages is syntactically correct and safe from XSS by default?

easy

A. <div v-html="userInput"></div>

B. <div>{{ userInput }}</div>

C. <div v-text=userInput></div>

D. <div>{{ userInput</div> }}

Solution

1. Step 1: Check syntax correctness

   <div>{{ userInput }}</div> uses correct Vue syntax with double curly braces and quotes are properly placed.

2. Step 2: Check XSS safety

   <div>{{ userInput }}</div> escapes content automatically, making it safe. <div v-html="userInput"></div> uses v-html which inserts raw HTML and can be unsafe. <div v-text=userInput></div> misses quotes around the binding value, causing syntax error. <div>{{ userInput</div> }} has mismatched braces causing syntax error.

3. Final Answer:

   <div>{{ userInput }}</div> -> Option B

4. Quick Check:

   Correct syntax + auto-escape = D [OK]

Hint: Use {{ }} with quotes for safe, correct syntax [OK]

Common Mistakes:

• Using v-html without sanitizing input
• Omitting quotes in directives
• Mismatching curly braces

3. Given the Vue template code:
<pre><template> <div>{{ userInput }}</div> <div v-html="userInput"></div> </template> And userInput is '<img src=x onerror=alert(1)>', what will be rendered in the browser?

medium

A. The first div shows the raw HTML tag as text; the second div executes the alert popup.

B. Both divs show the raw HTML tag as text without executing alert.

C. Both divs execute the alert popup.

D. The first div executes alert; the second div shows raw HTML tag as text.

Solution

1. Step 1: Analyze the first div with {{ userInput }}

   Vue escapes the content, so the HTML tag is shown as plain text, no alert runs.

2. Step 2: Analyze the second div with v-html

   v-html inserts raw HTML, so the <img> tag runs and triggers the alert.

3. Final Answer:

   The first div shows the raw HTML tag as text; the second div executes the alert popup. -> Option A

4. Quick Check:

   v-html inserts raw HTML = A [OK]

Hint: v-html runs HTML, {{ }} escapes it [OK]

Common Mistakes:

• Assuming both divs escape content
• Thinking v-html escapes content
• Confusing which div triggers alert

4. You have this Vue template:

<div v-html="userContent"></div>

User input is not sanitized. What is the best fix to prevent XSS?

medium

A. Replace v-html with {{ userContent }} to auto-escape

B. Keep v-html but add v-text on the same element

C. Use v-html but trust all user input as safe

D. Wrap v-html inside a <script> tag

Solution

1. Step 1: Identify the risk of v-html with unsanitized input

   v-html inserts raw HTML, so unsanitized user input can cause XSS attacks.

2. Step 2: Choose a safe alternative

   Replacing v-html with {{ userContent }} escapes content automatically, preventing XSS.

3. Final Answer:

   Replace v-html with {{ userContent }} to auto-escape -> Option A

4. Quick Check:

   Use {{ }} to escape user input safely = C [OK]

Hint: Avoid v-html with unsafe input; use {{ }} instead [OK]

Common Mistakes:

• Adding v-text does not sanitize v-html content
• Trusting all user input without sanitization
• Using script tags incorrectly

5. You want to display user comments that may contain safe HTML tags like <b> and <i> but prevent XSS in Vue. Which approach is best?

hard

A. Use {{ comment }} to escape all HTML, showing tags as text

B. Use v-html directly without sanitizing user comments

C. Use v-html with a sanitizer function that removes unsafe tags before binding

D. Replace <b> and <i> tags with <script> tags

Solution

1. Step 1: Understand the need to allow some HTML but block unsafe tags

   Using v-html allows HTML rendering but can cause XSS if input is unsafe.

2. Step 2: Use a sanitizer to clean user input

   Sanitizing removes dangerous tags/scripts but keeps safe tags like <b> and <i>.

3. Step 3: Bind sanitized content with v-html

   This approach safely renders allowed HTML while preventing XSS.

4. Final Answer:

   Use v-html with a sanitizer function that removes unsafe tags before binding -> Option C

5. Quick Check:

   Sanitize input before v-html = B [OK]

Hint: Sanitize user HTML before v-html to allow safe tags [OK]

Common Mistakes:

• Using v-html without sanitizing
• Escaping all HTML losing formatting
• Replacing safe tags with script tags