<?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 03:58:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233407</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233407</link>
      <description>EUVD-2026-233407</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233407</guid>
    </item>
    <item>
      <title>fkie_cve-2022-41938</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-41938</link>
      <description>&lt;p&gt;Flarum is an open source discussion platform. Flarum&amp;#39;s page title system allowed for page titles to be converted into HTML DOM nodes when pages were rendered. The change was made after `v1.5` and was not noticed. This allowed an attacker to inject malicious HTML markup using a discussion title input, either by creating a new discussion or renaming one. The XSS attack occurs after a visitor opens the relevant discussion page. All communities running Flarum from `v1.5.0` to `v1.6.1` are impacted. The vulnerability has been fixed and published as flarum/core `v1.6.2`. All communities running Flarum from `v1.5.0` to `v1.6.1` have to upgrade as soon as possible to v1.6.2. There are no known workarounds for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flarum is an open source discussion platform. Flarum&amp;#39;s page title system allowed for page titles to be converted into HTML DOM nodes when pages were rendered. The change was made after `v1.5` and was not noticed. This allowed an attacker to inject malicious HTML markup using a discussion title input, either by creating a new discussion or renaming one. The XSS attack occurs after a visitor opens the relevant discussion page. All communities running Flarum from `v1.5.0` to `v1.6.1` are impacted. The vulnerability has been fixed and published as flarum/core `v1.6.2`. All communities running Flarum from `v1.5.0` to `v1.6.1` have to upgrade as soon as possible to v1.6.2. There are no known workarounds for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-41938</guid>
    </item>
    <item>
      <title>GHSA-7x4w-j98p-854x — Cross site scripting vulnerability with discussion titles</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7x4w-j98p-854x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/core&lt;/p&gt;
&lt;p&gt;Flarum&amp;#39;s page title system allowed for page titles to be converted into HTML DOM nodes when pages were rendered. The change was made after `v1.5` and was not noticed.&lt;/p&gt;
&lt;p&gt;This allowed an attacker to inject malicious HTML markup using a discussion title input, either by creating a new discussion or renaming one. The XSS attack occurs after a visitor opens the relevant discussion page.&lt;/p&gt;
&lt;p&gt;### Impact
All communities running Flarum from `v1.5.0` to `v1.6.1` are impacted.&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been fixed and published as flarum/core `v1.6.2`. All communities running Flarum from `v1.5.0` to `v1.6.1` have to upgrade as soon as possible to v1.6.2 using:&lt;/p&gt;
&lt;p&gt;```
composer update --prefer-dist --no-dev -a -W
```&lt;/p&gt;
&lt;p&gt;You can then confirm you run the latest version using:&lt;/p&gt;
&lt;p&gt;```
composer show flarum/core
```&lt;/p&gt;
&lt;p&gt;### Workarounds
**None**&lt;/p&gt;
&lt;p&gt;### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.&lt;/p&gt;
&lt;p&gt;For support questions create a discussion at https://discuss.flarum.org/t/support.&lt;/p&gt;
&lt;p&gt;A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing [security@flarum.org](mailto:security@flarum.org), and we will address it promptly.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/core&lt;/p&gt;
&lt;p&gt;Flarum&amp;#39;s page title system allowed for page titles to be converted into HTML DOM nodes when pages were rendered. The change was made after `v1.5` and was not noticed.&lt;/p&gt;
&lt;p&gt;This allowed an attacker to inject malicious HTML markup using a discussion title input, either by creating a new discussion or renaming one. The XSS attack occurs after a visitor opens the relevant discussion page.&lt;/p&gt;
&lt;p&gt;### Impact
All communities running Flarum from `v1.5.0` to `v1.6.1` are impacted.&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been fixed and published as flarum/core `v1.6.2`. All communities running Flarum from `v1.5.0` to `v1.6.1` have to upgrade as soon as possible to v1.6.2 using:&lt;/p&gt;
&lt;p&gt;```
composer update --prefer-dist --no-dev -a -W
```&lt;/p&gt;
&lt;p&gt;You can then confirm you run the latest version using:&lt;/p&gt;
&lt;p&gt;```
composer show flarum/core
```&lt;/p&gt;
&lt;p&gt;### Workarounds
**None**&lt;/p&gt;
&lt;p&gt;### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.&lt;/p&gt;
&lt;p&gt;For support questions create a discussion at https://discuss.flarum.org/t/support.&lt;/p&gt;
&lt;p&gt;A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing [security@flarum.org](mailto:security@flarum.org), and we will address it promptly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7x4w-j98p-854x</guid>
    </item>
    <item>
      <title>gsd-2022-41938</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-41938</link>
      <description>gsd-2022-41938</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-41938</guid>
    </item>
  </channel>
</rss>
