is applied unchanged to the live DOM attribute when an attacker can influence the content of a translation file or the translation-backend response — for example, via a compromised translation CDN, user-contributed locales, a MITM on a plain-HTTP backend, or write access to the translation JSON. This issue was patched in version 4.0.8.", "datePublished": "2026-05-07T20:01:59Z", "dateModified": "2026-05-11T18:04:43Z", "keywords": "CVE-2026-41692, vulnerability, CVE, security, i18nextify, i18next", "about": { "@type": "SoftwareApplication", "name": "i18nextify", "applicationCategory": "SecurityApplication", "operatingSystem": "All" } }
CVE-2026-41692 MEDIUM

CVE-2026-41692: i18nextify is vulnerable to DOM XSS via javascript:/data: URL schemes in translated href/src attributes

Vendor I18Next
Product i18nextify
Weakness CWE-79 · XSS
Published May 7, 2026
Last update May 11, 2026

CVSS base score

4.7/10
Attack vector Network
Attack complexity High
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions prior to 4.0.8 substitute {{key}} interpolation tokens inside src and href attribute values with the raw string returned by i18next.t(). The substitution logic in src/localize.js (the replaceInside handler) only guards against a duplicated http:// origin prefix — it does not validate the URL scheme of the substituted value. A translated value such as javascript:alert(1) or data:text/html,<script>...</script> is applied unchanged to the live DOM attribute when an attacker can influence the content of a translation file or the translation-backend response — for example, via a compromised translation CDN, user-contributed locales, a MITM on a plain-HTTP backend, or write access to the translation JSON. This issue was patched in version 4.0.8.

Key dates

02Disclosure timeline

May 7, 2026 CVE published
May 11, 2026 Record updated

Related vulnerabilities

04Related CVE