Technical impact
Vue I18n’s escapeParameter feature fails to escape named interpolation values when a translation call is supplied with both a list and named values. Because escapeParams() processes only the list branch, any attacker‑controlled named data is rendered verbatim as HTML. This flaw allows insertion of malicious markup, including phishing links and forms, and can enable script execution when the application renders the translation in an HTML context or when bypassing certain sanitizers. The effect is a Classic Reflected XSS that can compromise confidentiality, integrity, and availability of the web application and its users.
Affected Systems
Affected users of intlify:vue-i18n from version 9.0.0‑beta.5 through 11.4.14 and from 12.0.0‑alpha.5 (prior to the release that fixed the issue). Any project that uses these Vue I18n versions and renders translations in a browser as HTML while passing untrusted named values together with a list is vulnerable.
Risk and Exploitability
The CVSS score of 2.1 indicates low severity, and currently there is no EPSS score available; the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is through front‑end code that accepts user input for translation parameters and renders the resulting string as HTML. An attacker could craft input that triggers the vulnerability by embedding malicious script or markup in named values while also supplying a list, and then accessing the affected page. Given the low CVSS and lack of exploitation data, the risk is moderate but the potential impact of XSS warrants attention.
Github GHSA