Quick answers
- Is CVE-2025-53892 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-53892 being exploited in the wild.
- How severe is CVE-2025-53892?
- Medium severity, with a CVSS score of 4, published 16 July 2025.
- Which products and versions are affected?
- @intlify/core (npm) SEMVER:introduced=9.0.0,fixed=9.14.5; @intlify/core-base (npm) SEMVER:introduced=9.0.0,fixed=9.14.5; @intlify/vue-i18n-core (npm) SEMVER:introduced=9.2.0,fixed=9.14.5; petite-vue-i18n (npm) SEMVER:introduced=10.0.0,fixed=10.0.8; and 1 more.
- Is there a fix for CVE-2025-53892?
- Yes. @intlify/core (npm): upgrade to 9.14.5 or later; @intlify/core-base (npm): upgrade to 9.14.5 or later; @intlify/vue-i18n-core (npm): upgrade to 9.14.5 or later; petite-vue-i18n (npm): upgrade to 10.0.8 or later; vue-i18n (npm): upgrade to 9.14.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-53892 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-53892?
- Check whether you run @intlify/core (npm), @intlify/core-base (npm), @intlify/vue-i18n-core (npm) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @intlify/core (npm): upgrade to 9.14.5 or later
npm install @intlify/core@9.14.5 - @intlify/core-base (npm): upgrade to 9.14.5 or later
npm install @intlify/core-base@9.14.5 - @intlify/vue-i18n-core (npm): upgrade to 9.14.5 or later
npm install @intlify/vue-i18n-core@9.14.5 - petite-vue-i18n (npm): upgrade to 10.0.8 or later
npm install petite-vue-i18n@10.0.8 - vue-i18n (npm): upgrade to 9.14.5 or later
npm install vue-i18n@9.14.5
Technical details
This is a DOM-based XSS vulnerability in vue-i18n's escapeParameterHtml option, which is intended to sanitize interpolated parameters against HTML injection. The vulnerability exists because the escaping mechanism does not properly sanitize HTML attribute contexts, specifically event handler attributes like onerror. An attacker can craft a translation string containing an HTML tag with a malicious event handler (e.g., <img src=x onerror="malicious code">) and use v-html directive to render it, bypassing the escapeParameterHtml protection. No special privileges or authentication is required; the attack only requires user interaction with rendering the translated content. Patches are available in vue-i18n 9.14.5, 10.0.8, 11.1.10 and related @intlify packages with the same version constraints.
Affected products
- Intlify vue-i18n 9.0.0–11.1.9
- Intlify @intlify/core 9.0.0–11.1.9
- Intlify @intlify/core-base 9.0.0–11.1.9
- Intlify @intlify/vue-i18n-core 9.2.0–11.1.9
- Intlify petite-vue-i18n 10.0.0–11.1.9
Identifiers
- CVE-2025-53892
- GHSA-x8qp-wqqm-57ph
Timeline
- 2025-07-16: disclosed: GHSA-x8qp-wqqm-57ph and CVE-2025-53892 published
- 2025-07-16: patched: Patches released: vue-i18n 9.14.5, 10.0.8, 11.1.10 and related @intlify packages