Summary
vue-i18n's escapeParameterHtml does not prevent DOM-based XSS through its tag attributes
The escapeParameterHtml: true option in Vue I18n is designed to protect against HTML/script injection by escaping interpolated parameters. However, 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.
Details
When escapeParameterHtml: true is enabled, it correctly escapes common injection points.
However, it does not sanitize entire attribute contexts, which can be used as XSS vectors via:
<img src=x onerror=alert(1)>
PoC
In your Vue I18n configuration:
const i18n = createI18n({
escapeParameterHtml: true,
messages: {
en: {
vulnerable: 'Caution: <img src=x onerror="{payload}">'
}
}
});
Use this interpolated payload:
const payload = '<script>alert("xss")</script>';
Render the translation using v-html (even not using v-html):
<p v-html="$t('vulnerable', { payload })"></p>
Expected: escaped content should render as text, not execute.
Actual: script executes in some environments (or the payload is partially parsed as HTML).
Impact
This creates a DOM-based Cross-Site Scripting (XSS) vulnerability despite enabling a security option (escapeParameterHtml) .
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
vue-i18n to 9.14.5 or later; vue-i18n to 10.0.8 or later; vue-i18n to 11.1.10 or later; @intlify/core to 9.14.5 or later; @intlify/core to 10.0.8 or later; @intlify/core to 11.1.10 or later; @intlify/core-base to 9.14.5 or later; @intlify/core-base to 10.0.8 or later; @intlify/core-base to 11.1.10 or later; @intlify/vue-i18n-core to 9.14.5 or later; @intlify/vue-i18n-core to 10.0.8 or later; @intlify/vue-i18n-core to 11.1.10 or later; petite-vue-i18n to 10.0.8 or later; petite-vue-i18n to 11.1.10 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-53892? CVE-2025-53892 is a medium-severity cross-site scripting (XSS) vulnerability in vue-i18n (npm), affecting versions >= 9.0.0, < 9.14.5. It is fixed in 9.14.5, 10.0.8, 11.1.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which packages are affected by CVE-2025-53892?
vue-i18n(npm) (versions >= 9.0.0, < 9.14.5)@intlify/core(npm) (versions >= 9.0.0, < 9.14.5)@intlify/core-base(npm) (versions >= 9.0.0, < 9.14.5)@intlify/vue-i18n-core(npm) (versions >= 9.2.0, < 9.14.5)petite-vue-i18n(npm) (versions >= 10.0.0, < 10.0.8)
- Is there a fix for CVE-2025-53892? Yes. CVE-2025-53892 is fixed in 9.14.5, 10.0.8, 11.1.10. Upgrade to this version or later.
- Is CVE-2025-53892 exploitable, and should I be worried? Whether CVE-2025-53892 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-53892 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-53892?
- Upgrade
vue-i18nto 9.14.5 or later - Upgrade
vue-i18nto 10.0.8 or later - Upgrade
vue-i18nto 11.1.10 or later - Upgrade
@intlify/coreto 9.14.5 or later - Upgrade
@intlify/coreto 10.0.8 or later - Upgrade
@intlify/coreto 11.1.10 or later - Upgrade
@intlify/core-baseto 9.14.5 or later - Upgrade
@intlify/core-baseto 10.0.8 or later - Upgrade
@intlify/core-baseto 11.1.10 or later - Upgrade
@intlify/vue-i18n-coreto 9.14.5 or later - Upgrade
@intlify/vue-i18n-coreto 10.0.8 or later - Upgrade
@intlify/vue-i18n-coreto 11.1.10 or later - Upgrade
petite-vue-i18nto 10.0.8 or later - Upgrade
petite-vue-i18nto 11.1.10 or later
- Upgrade