Technical impact
i18next-http-backend allows translation resources to be loaded by a backend in Node.js, browsers, and Deno. Prior to v4.0.4, the interpolation logic inserts language (lng) and namespace (ns) values directly into loadPath or addPath templates without rejecting ampersand (&), equals (=), or semicolon (;) query separators. Because these values are reflected in the query string, an attacker that controls lng or ns can append or override additional query parameters in translation requests. This can expose data from other namespaces, reveal multi‑tenant information, or modify backend behavior in the context of the application's network permissions. The flaw is a form of query‑parameter injection.
Affected Systems
Vendors: i18next. Product: i18next-http-backend. Versions affected: any release before 4.0.4. The issue applies to environments that use the backend for translation loading in Node.js, browsers, or Deno.
Risk and Exploitability
CVSS scoring indicates a low severity (3.7). EPSS score is 0.28% (< 1%), and the vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that an attacker must supply attacker‑controlled lng or ns values to exploit the flaw. While the exploit requires application‑level knowledge of translation requests, the reflected parameter injection is straightforward and can be achieved by appending & or = characters to language or namespace strings. The potential impact of leaking sensitive translation data or manipulating backend requests makes the risk moderate despite the low CVSS figure.
Github GHSA