<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 15:47:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-310014</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310014</link>
      <description>EUVD-2026-310014</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310014</guid>
    </item>
    <item>
      <title>fkie_cve-2026-41692</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-41692</link>
      <description>&lt;p&gt;i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions 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 (the replaceInside handler) 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,&amp;lt;script&amp;gt;...&amp;lt;/script&amp;gt; is applied unchanged to the live DOM attribute when an attacker can influence the content of a translation file or the translation-backend response — for example, via a compromised translation CDN, user-contributed locales, a MITM on a plain-HTTP backend, or write access to the translation JSON. This issue was patched in version 4.0.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions 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 (the replaceInside handler) 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,&amp;lt;script&amp;gt;...&amp;lt;/script&amp;gt; is applied unchanged to the live DOM attribute when an attacker can influence the content of a translation file or the translation-backend response — for example, via a compromised translation CDN, user-contributed locales, a MITM on a plain-HTTP backend, or write access to the translation JSON. This issue was patched in version 4.0.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-41692</guid>
    </item>
    <item>
      <title>GHSA-6457-mxpq-4fqq — i18nextify has DOM XSS via javascript:/data: URL schemes in translated href/src attributes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6457-mxpq-4fqq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: i18nextify&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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,&amp;lt;script&amp;gt;...&amp;lt;/script&amp;gt;` is applied unchanged to the live DOM attribute.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- Set any `href` on an anchor to a `javascript:` URI, executing arbitrary JavaScript when the victim clicks the link.
- Set any `src` on `&amp;lt;iframe&amp;gt;`, `&amp;lt;object&amp;gt;`, or `&amp;lt;embed&amp;gt;` to a `data:text/html` URI containing a full script payload that runs in the page&amp;#39;s origin.
- Use `vbscript:` on legacy IE installations or `file:` for local-resource navigation attacks.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Also fixed in 4.0.8&lt;/p&gt;
&lt;p&gt;- **`debug` / `saveMissing` URL…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: i18nextify&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;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,&amp;lt;script&amp;gt;...&amp;lt;/script&amp;gt;` is applied unchanged to the live DOM attribute.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;- Set any `href` on an anchor to a `javascript:` URI, executing arbitrary JavaScript when the victim clicks the link.
- Set any `src` on `&amp;lt;iframe&amp;gt;`, `&amp;lt;object&amp;gt;`, or `&amp;lt;embed&amp;gt;` to a `data:text/html` URI containing a full script payload that runs in the page&amp;#39;s origin.
- Use `vbscript:` on legacy IE installations or `file:` for local-resource navigation attacks.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Also fixed in 4.0.8&lt;/p&gt;
&lt;p&gt;- **`debug` / `saveMissing` URL…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6457-mxpq-4fqq</guid>
    </item>
  </channel>
</rss>
