fix(deps): update dependency vue-i18n to v9.14.5 [security] by renovate[bot] · Pull Request #562 · prefabs-tech/vue

renovate · 2025-03-07T16:10:54Z

This PR contains the following updates:

Package	Change	Age	Confidence
vue-i18n (source)	`9.1.10` -> `9.14.5`

GitHub Vulnerability Alerts

CVE-2025-27597

Vulnerability type:
Prototype Pollution

Vulnerability Location(s):

# v9.1
node_modules/@&#8203;intlify/message-resolver/index.js

# v9.2 or later
node_modules/@&#8203;intlify/vue-i18n-core/index.js

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:

// install the package with the latest version
~$ npm install @&#8203;intlify/message-resolver@9.1.10
// run the script mentioned below 
~$ node poc.js
//The expected output (if the code still vulnerable) is below. 
// Note that the output may slightly differs from function to another.
Before Attack:  {}
After Attack:  {"pollutedKey":123}

// poc.js
(async () => {
    const lib = await import('@&#8203;intlify/message-resolver');
    var someObj = {}
    console.log("Before Attack: ", JSON.stringify({}.__proto__));
    try {
        // for multiple functions, uncomment only one for each execution.
        lib.handleFlatJson ({ "__proto__.pollutedKey": "pollutedValue" })
    } catch (e) { }
    console.log("After Attack: ", JSON.stringify({}.__proto__));
    delete Object.prototype.pollutedKey;
})();

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:

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) .

Release Notes

intlify/vue-i18n (vue-i18n)

Conversation

renovate bot commented Mar 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

GitHub Vulnerability Alerts

Summary

Details

PoC

Impact

Release Notes

What's Changed

🔒 Security Fixes

What's Changed

🐛 Bug Fixes

What's Changed

🔒 Security Fixes

What's Changed

🔒 Security Fixes

What's Changed

🐛 Bug Fixes

What's Changed

⚡ Improvement Features

What's Changed

💥 Breaking Changes

What's Changed

🐛 Bug Fixes

What's Changed

⚠️ Deprecated Features

⚡ Improvement Features

📝️ Documentations

New Contributors

What's Changed

🐛 Bug Fixes

👕 Refactoring

What's Changed

🌟 Features

What's Changed

🐛 Bug Fixes

What's Changed

🌟 Features

New Contributors

What's Changed

🐛 Bug Fixes

New Contributors

What's Changed

⚡ Improvement Features

📝️ Documentations

New Contributors

What's Changed

🌟 Features

📝️ Documentations

New Contributors

What's Changed

🐛 Bug Fixes

📝️ Documentations

New Contributors

What's Changed

⚡ Improvement Features

📈 Performance Fixes

📝️ Documentations

New Contributors

What's Changed

🌟 Features

What's Changed

⚡ Improvement Features

What's Changed

🌟 Features

What's Changed

🐛 Bug Fixes

New Contributors

What's Changed

🐛 Bug Fixes

What's Changed

🐛 Bug Fixes

New Contributors

What's Changed

🐛 Bug Fixes

What's Changed

🐛 Bug Fixes

What's Changed

🌟 Features

renovate bot commented Mar 7, 2025 •

edited

Loading

Node.js Dual packages (`cjs` / `mjs`)

`allowComposition` option