LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16008: i18next is a language translation framework.

i18next is a language translation framework. Because of how the interpolation is implemented, making replacements from the dictionary one at a time, untrusted user input can use the name of one of the dictionary keys to inject script into the browser. This affects i18next <=1.10.2.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-16008 is a cross-site scripting issue in old i18next versions. If a website uses i18next <=1.10.2 and lets untrusted input interact with translation interpolation, an attacker may cause script to run in a user's browser. No active exploitation is cited in the supplied sources.

Executive priority

Prioritize remediation for internet-facing applications that use legacy i18next in browser-rendered flows. This is not KEV-supported emergency evidence, but XSS can affect user trust, session security, and customer-facing application risk.

Technical view

The issue is CWE-79 in the i18next node module <=1.10.2. The source bundle says interpolation performs dictionary replacements one at a time, allowing untrusted input using a dictionary key name to inject script into browser output.

Likely exposure

Exposure is most likely in legacy JavaScript or Node applications that still depend on i18next <=1.10.2 and render translated browser content using user-influenced interpolation data.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not claim active exploitation. Practical risk depends on whether attacker-controlled values can reach affected interpolation paths and be rendered into browser-visible content.

Researcher notes

Evidence is limited to the CVE description, Node Security advisory reference, and i18next pull request. No CVSS vector, exploited-in-the-wild claim, or exact fixed release is provided in the source bundle.

Mitigation direction

  • Inventory i18next versions in package manifests and lockfiles.
  • Upgrade any i18next dependency at or below 1.10.2 using vendor guidance.
  • Review translation interpolation paths that accept user-controlled values.
  • Apply standard output escaping and sanitization where browser HTML is rendered.
  • Check the referenced pull request and advisory for fix details.

Validation and detection

  • Confirm deployed applications do not include i18next <=1.10.2.
  • Trace whether untrusted input reaches i18next interpolation data.
  • Use safe XSS regression tests without weaponized payloads.
  • Verify browser-rendered translated output remains escaped.
  • Retest after dependency updates and lockfile changes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-16008 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnei18next node module<=1.10.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.