CVE-2026-41692 i18nextify is vulnerable to DOM XSS via javascript:/data: URL schemes in translated href/src attributes
Attackers can execute arbitrary JavaScript in victim browsers by injecting malicious URL schemes into translation files processed by the i18nextify library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-41692?
CVE-2026-41692 is a medium-severity cross-site scripting vulnerability in i18nextify, published on 7 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2026-41692?
2 open source packages ship an affected version, including i18nextify. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
i18nextify npm | All versions | 4.0.8 |
i18nextify npm | All versions | 4.0.8 |
Products include I18next I18nextify.
How do I fix CVE-2026-41692?
Upgrade i18nextify to 4.0.8 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-41692 being exploited?
There is no known exploitation of CVE-2026-41692 in the wild and no public exploit code.
Sources
Also known as GHSA-6457-mxpq-4fqq.