Technical impact
Vue I18n’s escapeParameter feature fails to sanitize the value of an iframe’s srcdoc attribute when translation strings are rendered as HTML using v-html. The value is left active, allowing attackers to inject malicious content into the srcdoc that browsers interpret as a nested HTML document. Executing the content results in script execution in the victim’s browser, potentially compromising session cookies, local storage, or other client‑side data. The flaw is a classic web cross‑site scripting weakness, exposing the application to client‑side code injection.
Affected Systems
The issue affects Vue I18n distributed by intlify. Vulnerable releases include 9.14.5 and 10.0.8 (no longer supported), versions 11.1.10 through 11.4.14, and 12.0.0‑alpha.4 through 12.0.0‑alpha.5. The i18n‑t rendering path is not impacted, but any translation rendering with v‑html and escapeParameter enabled is vulnerable.
Risk and Exploitability
The CVSS score of 7.2 categorises the vulnerability as high severity. EPSS data is not available, and it is not listed in CISA’s KEV catalog, but the lack of mitigation in affected releases means that the weakness can be leveraged in any deployment that uses translations as raw HTML. Attackers can plant the malicious srcdoc content in translation files or dynamically injected strings; no privileged user interaction is required beyond viewing the page. Because the flaw is purely client‑side, exploitation is straightforward for anyone who can influence translation content. The combined factors signal a moderate‑to‑high risk that warrants prompt remediation.
Github GHSA