Description
Versions of i18next-locize-backend prior to 9.0.2 interpolate lng, ns, projectId, and version directly into the configured loadPath / privatePath / addPath / updatePath / getLanguagesPath URL templates with no path-component validation and no encoding.
Recommendation
Update the i18next-locize-backend package to the latest compatible version. Followings are version details:
- Affected version(s): < 9.0.2
- Patched version(s): 9.0.2
References
Could your website be exposed too?
SmartScanner can check your website for i18next-locize-backend has URL Injection via Unsanitized Path Parameters and gives you actionable findings to investigate.
Start a free scanRelated Issues
- i18next-http-backend has Path Traversal & URL Injection via Unsanitised lng/ns - CVE-2026-41691
- Kysely: JSON-path traversal injection via unsanitized path-leg metacharacters in `JSONPathBuilder.key()` / `.at()` - CVE-2026-44635
- SCEditor has DOM XSS via emoticon URL/HTML injection - CVE-2026-25581
- SQL Injection via unsanitized JSON path keys when ignoring/silencing compilation errors or using `Kysely<any>`. - CVE-2026-32763
You might also like:
See something that needs correcting? Let us knowUpdated May 13, 2026