Why security matters in Vue - Performance Evidence

Performance: Why security matters in Vue

HIGH IMPACT

Security issues in Vue apps can cause slowdowns due to extra processing or errors, impacting user experience and interaction speed.

Rendering user-generated content safely in Vue

Vue

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

Using text interpolation escapes HTML, preventing script execution and keeping rendering predictable and fast.

📈 Performance GainAvoids extra script execution and layout shifts, improving INP and overall responsiveness.

Rendering user-generated content safely in Vue

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 slowdowns from unexpected script execution.

📉 Performance CostTriggers extra script execution and potential layout thrashing from injected elements, increasing INP and causing jank.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Unsafe v-html with raw user input	Adds unpredictable nodes	Multiple reflows if scripts modify DOM	High paint cost due to layout shifts	[X] Bad
Safe text interpolation with escaped content	Stable DOM nodes	Single reflow on initial render	Low paint cost, no layout shifts	[OK] Good

Rendering Pipeline

Unsafe rendering of user content can inject scripts that run during or after paint, causing layout shifts and blocking input responsiveness.

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckPaint and Composite stages due to unexpected DOM changes and script execution

Core Web Vital Affected

INP

Security issues in Vue apps can cause slowdowns due to extra processing or errors, impacting user experience and interaction speed.

Optimization Tips

1Never use v-html with untrusted user input without sanitizing.

2Prefer text interpolation to escape HTML and prevent script injection.

3Check performance in DevTools for layout shifts and long tasks after rendering user content.

Performance Quiz - 3 Questions

What is a performance risk of using v-html with untrusted user input in Vue?

A It can run malicious scripts causing slowdowns and layout shifts

B It automatically optimizes rendering for faster paint

C It reduces DOM nodes and improves performance

D It caches content to speed up future renders

DevTools: Performance

How to check: Record a session while interacting with user-generated content. Look for long tasks or layout shifts after rendering.

What to look for: High INP values or unexpected layout shifts indicate unsafe rendering causing performance issues.

Practice

1. Why is security important when building Vue applications?

easy

A. To reduce the size of the Vue library

B. To make the app load faster

C. To protect users from malicious attacks like cross-site scripting (XSS)

D. To add more animations and effects

Solution

1. Step 1: Understand the purpose of security in web apps

   Security protects users and data from harmful actions like hacking or data theft.

2. Step 2: Identify common security risks in Vue apps

   Cross-site scripting (XSS) is a common risk where attackers inject harmful code into the app.

3. Final Answer:

   To protect users from malicious attacks like cross-site scripting (XSS) -> Option C

4. Quick Check:

   Security = Protect users from attacks [OK]

Hint: Security protects users from harmful code injections [OK]

Common Mistakes:

• Confusing security with performance
• Thinking security only affects backend
• Believing Vue automatically prevents all risks

2. Which Vue syntax is safe to display user content without risking XSS attacks?

easy

A. <div>{{ userContent }}</div>

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

C. <div>{{{ userContent }}}</div>

D. <div v-text="userContent"></div>

Solution

1. Step 1: Understand Vue's default escaping

   Using double curly braces {{ }} automatically escapes HTML, preventing XSS.

2. Step 2: Compare with other options

   v-html and triple braces {{{ }}} insert raw HTML, which can be unsafe. v-text also escapes but renders text only.

3. Final Answer:

   <div>{{ userContent }}</div> -> Option A

4. Quick Check:

   Double braces escape HTML = safe [OK]

Hint: Use {{ }} to safely display user content in Vue [OK]

Common Mistakes:

• Using v-html without sanitizing content
• Confusing triple braces with double braces
• Assuming v-text allows HTML rendering

3. What will be the rendered output of this Vue template if userInput is '<script>alert("XSS")</script>Hello'?

<template>
  <div>{{ userInput }}</div>
</template>

medium

A. <script>alert("XSS")</script>Hello (script runs)

B. Empty div with no content

C. Hello only

D. <script>alert("XSS")</script>Hello (script shown as text)

Solution

1. Step 1: Understand Vue's interpolation escaping

   Using {{ userInput }} escapes HTML tags, so script tags are shown as text, not executed.

2. Step 2: Predict the output

   The script tags appear as text, followed by 'Hello', so the full string is visible safely.

3. Final Answer:

   <script>alert("XSS")</script>Hello (script shown as text) -> Option D

4. Quick Check:

   Escaped HTML shows tags as text [OK]

Hint: {{ }} escapes HTML, so scripts show as text, not run [OK]

Common Mistakes:

• Thinking script runs inside {{ }}
• Expecting only 'Hello' to show
• Confusing raw HTML insertion with interpolation

4. You have this Vue code:

<template>
  <div v-html="rawHtml"></div>
</template>

<script setup>
const rawHtml = ''
</script>

What is the main security problem here?

medium

A. v-html renders raw HTML which can run malicious scripts

B. The img tag is invalid and causes syntax errors

C. Vue automatically sanitizes v-html content, so no problem

D. Using const for rawHtml causes reactivity issues

Solution

1. Step 1: Understand v-html behavior

   v-html inserts raw HTML into the DOM without escaping, so scripts can run.

2. Step 2: Identify the risk in the example

   The img tag has an onerror attribute that triggers alert(1), a common XSS attack vector.

3. Final Answer:

   v-html renders raw HTML which can run malicious scripts -> Option A

4. Quick Check:

   v-html = raw HTML injection risk [OK]

Hint: v-html inserts raw HTML; sanitize before use [OK]

Common Mistakes:

• Assuming Vue sanitizes v-html automatically
• Confusing syntax errors with security issues
• Thinking const affects security

5. You want to safely display user comments that may contain some HTML tags like <b> and <i> but prevent any scripts. Which approach best balances security and formatting in Vue?

hard

A. Escape all HTML tags and show comments as plain text

B. Sanitize user comments to allow only safe tags, then use v-html

C. Use v-html directly on user comments without filtering

D. Use triple braces {{{ comment }}} to render raw HTML

Solution

1. Step 1: Understand the need for safe HTML rendering

   Allowing some HTML tags improves formatting but raw HTML can be dangerous.

2. Step 2: Choose a method to allow safe tags only

   Sanitizing user input removes harmful scripts but keeps allowed tags, then v-html safely renders it.

3. Final Answer:

   Sanitize user comments to allow only safe tags, then use v-html -> Option B

4. Quick Check:

   Sanitize then v-html = safe formatted output [OK]

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

Common Mistakes:

• Using v-html without sanitizing
• Escaping all HTML losing formatting
• Using triple braces which is unsafe