Intlify Vue I18n's escapeParameterHtml does not prevent DOM-based XSS via tag attributes like onerror
intlify vue-i18n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| vue-i18n npm |
|
|
| @intlify/core npm |
|
intlify vue-i18n
| Product | Affected | Fixed in |
|---|---|---|
| vue-i18n npm |
|
|
| @intlify/core npm |
|
≥ 10.0.0 · < 10.0.8≥ 11.0.0 · < 11.1.10
|
| @intlify/core-base npm |
|
|
| @intlify/vue-i18n-core npm |
|
|
| petite-vue-i18n npm |
|
|
Vue I18n is the internationalization plugin for Vue.js. The escapeParameterHtml: true option in Vue I18n is designed to protect against HTML/script injection by escaping interpolated parameters. However, starting in version 9.0.0 and prior to versions 9.14.5, 10.0.8, and 11.1.0, this setting fails to prevent execution of certain tag-based payloads, such as <img src=x onerror=...>, if the interpolated value is inserted inside an HTML context using v-html. This may lead to a DOM-based XSS vulnerability, even when using escapeParameterHtml: true, if a translation string includes minor HTML and is rendered via v-html. Versions 9.14.5, 10.0.8, and 11.1.0 contain a fix for the issue.
From the CVE record · GitHub_M
Vue I18n's escapeParameterHtml option can fail to block certain tag-based payloads. An attacker who can control an interpolated value may cause script execution when a translation containing HTML is rendered with v-html, even with escapeParameterHtml enabled. The input does not specify whether authentication or other user interaction is required.
Teams using affected npm versions of vue-i18n, @intlify/core, @intlify/core-base, or @intlify/vue-i18n-core in the 9.x, 10.x, or 11.x ranges, or petite-vue-i18n in the 10.x or 11.x ranges, should check their dependencies.