` is applied unchanged","image":"https://o3.security/opengraph.png","datePublished":"2026-04-22T17:42:24Z","dateModified":"2026-05-11T13:53:13.645066Z","url":"https://o3.security/vulnerability/GHSA-6457-mxpq-4fqq","inLanguage":"en","author":{"@id":"https://o3.security/#organization"},"publisher":{"@id":"https://o3.security/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://o3.security/vulnerability/GHSA-6457-mxpq-4fqq"},"speakable":{"@type":"SpeakableSpecification","cssSelector":["h1",".vuln-summary",".vuln-severity",".vuln-mitigation"]},"about":[{"@type":"SoftwareApplication","name":"i18nextify","applicationCategory":"npm","softwareVersion":"4.0.8"}],"citation":[{"@type":"WebPage","url":"https://github.com/i18next/i18nextify/security/advisories/GHSA-6457-mxpq-4fqq"},{"@type":"WebPage","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-41692"},{"@type":"WebPage","url":"https://github.com/i18next/i18nextify/commit/16f23dbcdcf893673587f7a03355bf7ce0a0e49e"}]}` is applied unchanged","url":"https://o3.security/vulnerability/GHSA-6457-mxpq-4fqq","identifier":"GHSA-6457-mxpq-4fqq","datePublished":"2026-04-22T17:42:24Z","dateModified":"2026-05-11T13:53:13.645066Z","inLanguage":"en","license":"https://creativecommons.org/licenses/by/4.0/","keywords":["GHSA-6457-mxpq-4fqq","MEDIUM severity","CVE","vulnerability","security advisory"],"creator":{"@id":"https://o3.security/#organization"},"isAccessibleForFree":true,"variableMeasured":[{"@type":"PropertyValue","name":"CVSS Base Score","value":4.7,"description":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N"},{"@type":"PropertyValue","name":"Severity","value":"MEDIUM"}]}` is applied unchanged to the live DOM attribute.\n\n### Impact\n\nWhen an attacker can influence the content of a translation"}},{"@type":"Question","name":"How severe is GHSA-6457-mxpq-4fqq?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6457-mxpq-4fqq has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance."}},{"@type":"Question","name":"Which packages are affected by GHSA-6457-mxpq-4fqq?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6457-mxpq-4fqq affects the following packages: i18nextify (npm). Ecosystems affected: npm."}},{"@type":"Question","name":"How do I fix GHSA-6457-mxpq-4fqq?","acceptedAnswer":{"@type":"Answer","text":"Update i18nextify to 4.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6457-mxpq-4fqq is resolved across your whole dependency graph."}},{"@type":"Question","name":"How do I detect GHSA-6457-mxpq-4fqq in my npm dependencies?","acceptedAnswer":{"@type":"Answer","text":"Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for i18nextify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match."}},{"@type":"Question","name":"How do I mitigate GHSA-6457-mxpq-4fqq if there is no patch (or I can't update yet)?","acceptedAnswer":{"@type":"Answer","text":"If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands."}},{"@type":"Question","name":"How does O3 Security protect against GHSA-6457-mxpq-4fqq?","acceptedAnswer":{"@type":"Answer","text":"O3 pinpoints whether GHSA-6457-mxpq-4fqq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed."}},{"@type":"Question","name":"Is GHSA-6457-mxpq-4fqq actively exploited in the wild?","acceptedAnswer":{"@type":"Answer","text":"No public exploit code has been indexed for GHSA-6457-mxpq-4fqq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure."}},{"@type":"Question","name":"When was GHSA-6457-mxpq-4fqq published, and has it been updated?","acceptedAnswer":{"@type":"Answer","text":"GHSA-6457-mxpq-4fqq was published on April 22, 2026 and was last updated on May 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting."}}]}
Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-6457-mxpq-4fqq

MEDIUM

GHSA-6457-mxpq-4fqq is a medium-severity (CVSS 4.7) vulnerability in i18nextify. O3 Security confirms whether GHSA-6457-mxpq-4fqq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

i18nextify has DOM XSS via javascript:/data: URL schemes in translated href/src attributes

Also known asCVE-2026-41692
Published
Apr 22, 2026
Updated
May 11, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
📦i18nextify

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Versions of i18nextify 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 (replaceInside handler around line 122) 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,<script>...</script> is applied unchanged to the live DOM attribute.

Impact

When an attacker can influence the content of a translation file or the translation-backend response — compromised translation CDN, user-contributed locales, MITM on a plain-HTTP backend, write access to the translation JSON — they can:

  • Set any href on an anchor to a javascript: URI, executing arbitrary JavaScript when the victim clicks the link.
  • Set any src on <iframe>, <object>, or <embed> to a data:text/html URI containing a full script payload that runs in the page's origin.
  • Use vbscript: on legacy IE installations or file: for local-resource navigation attacks.

This path is distinct from the general i18nextify design that intentionally renders HTML from translations — href/src schemes are narrow and attack-specific, and no legitimate translation needs javascript: or data:. The fix therefore blocks these schemes outright without changing other behaviour.

Also fixed in 4.0.8

  • debug / saveMissing URL-parameter substring match. The previous detection window.location.search.indexOf('debug=true') > -1 matched the substring anywhere in the query string. A URL like ?nosaveMissing=true silently enabled saveMissing mode, causing the victim's browser to POST every unknown translation key to the configured addPath — a form of CSRF-style abuse of missing-key reporting. ?track_debug=true enabled verbose debug logging, leaking i18next internals to the console. Now uses URLSearchParams for exact parameter matching.
  • Optional sanitize(html, ctx) hook. The library's core purpose is to render HTML from translations — a behaviour that is safe only when the translation source is fully trusted. Applications with partially-trusted sources (user-contributed locales, third-party CDN, MITM-exposed HTTP backend) can now wire a sanitizer (e.g. DOMPurify) via i18next.options.sanitize. Defaults to pass-through to preserve existing behaviour for the main use case.

Affected versions

All versions of i18nextify prior to 4.0.8.

Patch

Fixed in 4.0.8. The URL-scheme blocklist is ^\s*(javascript|data|vbscript|file)\s*: (case-insensitive) applied to each translated value before it is joined back into the href/src attribute. Values matching the blocklist are replaced with an empty string so the attribute becomes harmless rather than leaving the attacker's URL in place.

Workarounds

No workaround short of upgrading. If you cannot upgrade immediately, audit every translation file for javascript:, data:, vbscript:, and file: prefixes in any value that may reach an href/src position, and restrict translation-file write access to trusted operators. Serving translations over HTTPS and pinning the translation backend to an internal origin reduce the MITM surface.

Credits

Discovered via an internal security audit of the i18next ecosystem.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmi18nextifyall versions4.0.8

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for i18nextify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update i18nextify to 4.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6457-mxpq-4fqq is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6457-mxpq-4fqq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6457-mxpq-4fqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Versions of `i18nextify` 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` (`replaceInside` handler around line 122) 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,<script>...</script>` is applied unchanged to the live DOM attribute. ### Impact When an attacker can influence the content of a translation
O3 Security · Impact-Aware SCA

Is GHSA-6457-mxpq-4fqq in your dependencies?

O3 detects GHSA-6457-mxpq-4fqq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works