# CVE-2025-53892: Intlify Vue I18n's escapeParameterHtml does not prevent DOM-based XSS via tag attributes like onerror > Attackers can execute arbitrary JavaScript via DOM-based XSS in Vue I18n when using v-html with escapeParameterHtml enabled. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 16 Jul 2025 - **Updated:** 22 Jul 2025 - **Also known as:** GHSA-x8qp-wqqm-57ph ## What is CVE-2025-53892? CVE-2025-53892 is a medium-severity cross-site scripting vulnerability in intlify vue-i18n, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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 , 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-53892? 28 open source packages ship an affected version, including @intlify/vue-i18n-core, @intlify/core and @intlify/core-base. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@intlify/vue-i18n-core` | npm | From 10.0.0 | 10.0.8 | | `@intlify/vue-i18n-core` | npm | From 10.0.0 | 10.0.8 | | `@intlify/vue-i18n-core` | npm | From 11.0.0 | 11.1.10 | | `@intlify/vue-i18n-core` | npm | From 11.0.0 | 11.1.10 | | `@intlify/vue-i18n-core` | npm | From 9.2.0 | 9.14.5 | | `@intlify/vue-i18n-core` | npm | From 9.2.0 | 9.14.5 | | `@intlify/core` | npm | From 10.0.0 | 10.0.8 | | `@intlify/core` | npm | From 10.0.0 | 10.0.8 | | `@intlify/core` | npm | From 11.0.0 | 11.1.10 | | `@intlify/core` | npm | From 11.0.0 | 11.1.10 | | `@intlify/core` | npm | From 9.0.0 | 9.14.5 | | `@intlify/core` | npm | From 9.0.0 | 9.14.5 | | `@intlify/core-base` | npm | From 10.0.0 | 10.0.8 | | `@intlify/core-base` | npm | From 10.0.0 | 10.0.8 | | `@intlify/core-base` | npm | From 11.0.0 | 11.1.10 | | `@intlify/core-base` | npm | From 11.0.0 | 11.1.10 | | `@intlify/core-base` | npm | From 9.0.0 | 9.14.5 | | `@intlify/core-base` | npm | From 9.0.0 | 9.14.5 | | `petite-vue-i18n` | npm | From 10.0.0 | 10.0.8 | | `petite-vue-i18n` | npm | From 10.0.0 | 10.0.8 | | `petite-vue-i18n` | npm | From 11.0.0 | 11.1.10 | | `petite-vue-i18n` | npm | From 11.0.0 | 11.1.10 | | `vue-i18n` | npm | From 10.0.0 | 10.0.8 | | `vue-i18n` | npm | From 10.0.0 | 10.0.8 | | `vue-i18n` | npm | From 11.0.0 | 11.1.10 | | `vue-i18n` | npm | From 11.0.0 | 11.1.10 | | `vue-i18n` | npm | From 9.0.0 | 9.14.5 | | `vue-i18n` | npm | From 9.0.0 | 9.14.5 | ## How do I fix CVE-2025-53892? Upgrade @intlify/vue-i18n-core to a fixed version for your release line: 10.0.8, 11.1.10 or 9.14.5. ## Is CVE-2025-53892 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53892 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-53892 and fix it if it is affected. What it is: CVE-2025-53892 is a medium-severity cross-site scripting vulnerability in intlify vue-i18n, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53892 exists. Affected packages and fixed versions: - @intlify/vue-i18n-core (npm): affected from 10.0.0; fixed in 10.0.8 - @intlify/vue-i18n-core (npm): affected from 10.0.0; fixed in 10.0.8 - @intlify/vue-i18n-core (npm): affected from 11.0.0; fixed in 11.1.10 - @intlify/vue-i18n-core (npm): affected from 11.0.0; fixed in 11.1.10 - @intlify/vue-i18n-core (npm): affected from 9.2.0; fixed in 9.14.5 - @intlify/vue-i18n-core (npm): affected from 9.2.0; fixed in 9.14.5 - @intlify/core (npm): affected from 10.0.0; fixed in 10.0.8 - @intlify/core (npm): affected from 10.0.0; fixed in 10.0.8 - @intlify/core (npm): affected from 11.0.0; fixed in 11.1.10 - @intlify/core (npm): affected from 11.0.0; fixed in 11.1.10 - @intlify/core (npm): affected from 9.0.0; fixed in 9.14.5 - @intlify/core (npm): affected from 9.0.0; fixed in 9.14.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-53892/ (Markdown: https://insights.sbomify.com/CVE-2025-53892/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53892 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53892 - OSV: https://osv.dev/vulnerability/CVE-2025-53892 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-53892/ Summaries are generated and may contain mistakes; the official description above is the record.