chore(deps): update dependency vue-i18n to v9.14.5 [security]#21
chore(deps): update dependency vue-i18n to v9.14.5 [security]#21renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Reviewer's Guide by SourceryThis PR updates the vue-i18n dependency from version 9.13.1 to 9.14.2 to address two critical security vulnerabilities: an XSS vulnerability (CVE-2024-52809) and a prototype pollution vulnerability (CVE-2024-52810). The update is implemented through dependency version changes in package.json and pnpm-lock.yaml files. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
CI Failure Feedback 🧐(Checks updated until commit 093c27b)
✨ CI feedback usage guide:The CI feedback tool (
In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR: where Configuration options
See more information about the |
093c27b to
9ae15af
Compare
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
9ae15af to
2423353
Compare
2423353 to
616a2a3
Compare
616a2a3 to
08de3a9
Compare
08de3a9 to
3b86138
Compare
This PR contains the following updates:
9.13.1→9.14.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
CVE-2024-52809
Vulnerability type
XSS
Description
vue-i18n can be passed locale messages to
createI18noruseI18n.we can then translate them using
tand$t.vue-i18n has its own syntax for local messages, and uses a message compiler to generate AST.
In order to maximize the performance of the translation function, vue-i18n uses bundler plugins such as
@intlify/unplugin-vue-i18nand bulder to convert the AST in advance when building the application.By using that AST as the locale message, it is no longer necessary to compile, and it is possible to translate using the AST.
The AST generated by the message compiler has special properties for each node in the AST tree to maximize performance. In the PoC example below, it is a
staticproperty, but that is just one of the optimizations.About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts
In general, the locale messages of vue-i18n are optimized during production builds using
@intlify/unplugin-vue-i18n,so there is always a property that is attached during optimization like this time.
But if you are using a locale message AST in development mode or your own, there is a possibility of XSS if a third party injects.
Reproduce (PoC)
Workarounds
Before v10.0.0, we can work around this vulnerability by using the regular compilation (
jit: falseof@intlify/unplugin-vue-i18nplugin configuration) way instead of jit compilation.References
CVE-2024-52810
Vulnerability type: Prototype Pollution
Affected Package:
Product: @intlify/shared
Version: 10.0.4
Vulnerability Location(s):
node_modules/@​intlify/shared/dist/shared.cjs:232:26Description:
The latest version of
@intlify/shared (10.0.4)is vulnerable to Prototype Pollution through the entry function(s)lib.deepCopy. An attacker can supply a payload withObject.prototypesetter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) the minimum consequence.Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.
PoC:
References
Prototype Pollution Leading to Remote Code Execution - An example of how prototype pollution can lead to command code injection.
OWASP Prototype Pollution Prevention Cheat Sheet - Best practices for preventing prototype pollution.
PortSwigger Guide on Preventing Prototype Pollution - A detailed guide to securing your applications against prototype pollution.
CVE-2025-27597
Vulnerability type:
Prototype Pollution
Vulnerability Location(s):
Description:
The latest version of
@intlify/message-resolver (9.1)and@intlify/vue-i18n-core (9.2 or later), (previous versions might also affected), is vulnerable to Prototype Pollution through the entry function(s)handleFlatJson. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence.Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.
PoC:
CVE-2025-53892
Summary
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:
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) .
Release Notes
intlify/vue-i18n (vue-i18n)
v9.14.5Compare Source
What's Changed
🔒 Security Fixes
Full Changelog: intlify/vue-i18n@v9.14.4...v9.14.5
v9.14.4Compare Source
What's Changed
🐛 Bug Fixes
Full Changelog: intlify/vue-i18n@v9.14.3...v9.14.4
v9.14.3Compare Source
What's Changed
🔒 Security Fixes
handleFlatJson, about details see GHSA-p2ph-7g93-hw3mFull Changelog: intlify/vue-i18n@v9.14.2...v9.14.3
v9.14.2Compare Source
What's Changed
🔒 Security Fixes
Full Changelog: intlify/vue-i18n@v9.14.1...v9.14.2
v9.14.1Compare Source
What's Changed
🐛 Bug Fixes
deepCopymutatessrcarguments by @BobbieGoede in #1975Full Changelog: intlify/vue-i18n@v9.14.0...v9.14.1
v9.14.0Compare Source
What's Changed
⚡ Improvement Features
Full Changelog: intlify/vue-i18n@v9.13.1...v9.14.0
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.