Cross-Site Scripting (XSS) in i18nextify (CVE-2026-41692)
Summary
Cross-site scripting in i18nextify (CVE-2026-41692). Risk of unauthorized operations or information disclosure. Exploitable via i18nextify. Mitigation: upgrade to 4.0.8 or later.
Original description
The description as published by the source.
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,... 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41692 has been found in i18nextify.
Attackers can target a specific entry point like i18nextify over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade i18nextify to 4.0.8 or later.
If unsure, ask your IT team or search "i18nextify CVE-2026-41692" on the vendor's site.
CVE-2026-41692 (i18nextify) — CWE-79 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: i18nextify / src / href / replaceInside
Patched: 4.0.8 — apply immediately
Workaround: No workaround short of upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in i18nextify. Attackers reach the vulnerable code path via i18nextify without authentication.
Check the vendor advisory for the affected versions of i18nextify. Attack surface: i18nextify / src / href / replaceInside.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to 4.0.8.
Workaround: No workaround short of upgrading.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'i18nextify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'i18nextify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
i18nextifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No workaround short of upgrading.パッチが適用されるまでの応急処置として、No workaround short of upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade i18nextify to 4.0.8ステージング環境で 4.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com