Vulnerability library
Security checkOctober 28, 2026

Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - @intlify/core

Understand the exposure, see the recommended fix, and check whether your own website has related weaknesses.

Low severitynpm@intlify/core

Check your website

Find this and other vulnerabilities with a free scan.

Your scan runs on your computer. No account required.

Description

When escapeParameter is enabled (escapeParameterHtml in the Legacy API), Vue I18n escapes the interpolation parameters before formatting a message. escapeParams() escapes either the list values or the named values, but not both: the two branches are joined by else. When a single call passes both, for example t(key, ['...'], { named: { ... } }), the named values reach the message without being escaped.

Recommendation

Update the @intlify/core package to the latest compatible version. Followings are version details:

  • Affected version(s): **>= 12.0.0-alpha.1, < 12.0.0-alpha.5 >= 9.0.0-beta.10, < 11.4.14**
  • Patched version(s): **12.0.0-alpha.5 11.4.14**

References

Could your website be exposed too?

SmartScanner can check your website for Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - @intlify/core and gives you actionable findings to investigate.

Start a free scan

Related Issues

See something that needs correcting? Let us knowUpdated October 28, 2026