How to fix: Vue v-html with computed expression
<div v-html="computed(userInput)"></div> evaluates a computed expression that mixes user data into HTML; any <script> or event-handler tags are inserted verbatim.
Why it matters
Attacker-controlled HTML executes JavaScript in the Vue app origin.
The `code-xss-vue-v-html-dynamic` check verifies that the server does not expose the `xss-vue-v-html-dynamic` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Sanitize the computed string with DOMPurify before binding to v-html.
- 2Use Mustache interpolation {{ value }} unless the HTML is provably safe.
- 3Adopt Trusted Types to gate v-html assignments.
Code examples
Always sanitize dynamic v-html bindings
<script setup lang="ts">
import DOMPurify from "dompurify";
import { computed, type PropType } from "vue";
const props = defineProps({ html: String });
const safe = computed(() => DOMPurify.sanitize(props.html ?? ""));
</script>
<template>
<div v-html="safe" />
</template>References
Detected automatically by VulnRadar. The check id is code-xss-vue-v-html-dynamic, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Vue v-html with computed expression?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-xss-vue-v-html-dynamic, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Vue v-html with computed expression map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.