i18next-http-backend 4.0.2 Protocol-Relative URL Injection via Namespace in interpolateUrl
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
The i18next-http-backend library, a plugin that loads translation files for the i18next internationalization framework in JavaScript applications, is affected. An attacker who controls the namespace value can redirect translation requests to a server they host, which can inject malicious content into the user interface and enable cross-site scripting.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
i18next-http-backend 4.0.2 contains an incomplete fix in interpolateUrl() that allows attackers to redirect translation requests by supplying an ns value starting with a slash. Attackers controlling the namespace value can form a protocol-relative URL in loadPath or addPath templates to load attacker-hosted translations, enabling UI content injection and cross-site scripting.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- i18next i18next-http-backend
From 4.0.2 · fixed in 4.0.3
- i18next-http-backendnpm
fixed in 4.0.3
- i18next-http-backendnpm
through 4.0.2