<?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 14:39:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-376011</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-376011</link>
      <description>EUVD-2026-376011</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-376011</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93747</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-93747</link>
      <description>&lt;p&gt;The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;telegram&amp;#39; profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST[&amp;#39;data&amp;#39;] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;telegram&amp;#39; profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST[&amp;#39;data&amp;#39;] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-93747</guid>
    </item>
    <item>
      <title>GHSA-584m-jf9m-5hp3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-584m-jf9m-5hp3</link>
      <description>&lt;p&gt;The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;telegram&amp;#39; profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST[&amp;#39;data&amp;#39;] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The wpForo Forum plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;telegram&amp;#39; profile field in versions up to, and including, 3.1.6. This is due to insufficient input sanitization and output escaping in the profile_update action — the raw $_POST[&amp;#39;data&amp;#39;] array is copied into a $custom_fields variable before validate() and sanitize() run, both of which operate only on a parallel $user reference, leaving $custom_fields unsanitized when it is persisted via update_custom_fields(); on render, wpforo_decode() reverses the entity encoding and the value is echoed without escaping in field_wrap_profile(). This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-584m-jf9m-5hp3</guid>
    </item>
  </channel>
</rss>
