<?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 07:53:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-221687</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221687</link>
      <description>EUVD-2026-221687</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221687</guid>
    </item>
    <item>
      <title>fkie_cve-2023-22487</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-22487</link>
      <description>&lt;p&gt;Flarum is a forum software for building communities. Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@&amp;#34;&amp;lt;username&amp;gt;&amp;#34;#p&amp;lt;id&amp;gt;` syntax. The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/&amp;lt;id&amp;gt;` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions. An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it&amp;#39;s possible to extract the discussion ID of all posts and combine all posts back together…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flarum is a forum software for building communities. Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@&amp;#34;&amp;lt;username&amp;gt;&amp;#34;#p&amp;lt;id&amp;gt;` syntax. The following behavior never changes no matter if the actor should be able to read the mentioned post or not: A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number. The `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/&amp;lt;id&amp;gt;` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions. An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward. The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events. The discussion payload is not leaked but using the mention HTML payload it&amp;#39;s possible to extract the discussion ID of all posts and combine all posts back together…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-22487</guid>
    </item>
    <item>
      <title>GHSA-22m9-m3ww-53h3 — Flarum post mentions can be used to read any post on the forum without access control</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-22m9-m3ww-53h3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/mentions&lt;/p&gt;
&lt;p&gt;Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@&amp;#34;&amp;lt;username&amp;gt;&amp;#34;#p&amp;lt;id&amp;gt;` syntax.&lt;/p&gt;
&lt;p&gt;The following behavior never changes no matter if the actor should be able to read the mentioned post or not:&lt;/p&gt;
&lt;p&gt;A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number.&lt;/p&gt;
&lt;p&gt;The `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/&amp;lt;id&amp;gt;` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions.&lt;/p&gt;
&lt;p&gt;An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward.&lt;/p&gt;
&lt;p&gt;### Impact
The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events.&lt;/p&gt;
&lt;p&gt;The discussion payload is not leaked but using the mention HTML payload it&amp;#39;s possible to extract the discussion ID of all posts and combine all posts back together into their original discussions eve…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/mentions&lt;/p&gt;
&lt;p&gt;Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@&amp;#34;&amp;lt;username&amp;gt;&amp;#34;#p&amp;lt;id&amp;gt;` syntax.&lt;/p&gt;
&lt;p&gt;The following behavior never changes no matter if the actor should be able to read the mentioned post or not:&lt;/p&gt;
&lt;p&gt;A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number.&lt;/p&gt;
&lt;p&gt;The `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/&amp;lt;id&amp;gt;` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions.&lt;/p&gt;
&lt;p&gt;An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward.&lt;/p&gt;
&lt;p&gt;### Impact
The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events.&lt;/p&gt;
&lt;p&gt;The discussion payload is not leaked but using the mention HTML payload it&amp;#39;s possible to extract the discussion ID of all posts and combine all posts back together into their original discussions eve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-22m9-m3ww-53h3</guid>
    </item>
    <item>
      <title>gsd-2023-22487</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-22487</link>
      <description>gsd-2023-22487</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-22487</guid>
    </item>
  </channel>
</rss>
