<?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>Fri, 23 Oct 2026 03:05:10 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-66918</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-66918</link>
      <description>cnvd-2021-66918</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-66918</guid>
    </item>
    <item>
      <title>EUVD-2026-23954</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-23954</link>
      <description>EUVD-2026-23954</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-23954</guid>
    </item>
    <item>
      <title>fkie_cve-2021-24535</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-24535</link>
      <description>&lt;p&gt;The Light Messages WordPress plugin through 1.0 is lacking CSRF check when updating it&amp;#39;s settings, and is not sanitising its Message Content in them (even with the unfiltered_html disallowed). As a result, an attacker could make a logged in admin update the settings to arbitrary values, and set a Cross-Site Scripting payload in the Message Content. Depending on the options set, the XSS payload can be triggered either in the backend only (in the plugin&amp;#39;s settings), or both frontend and backend.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Light Messages WordPress plugin through 1.0 is lacking CSRF check when updating it&amp;#39;s settings, and is not sanitising its Message Content in them (even with the unfiltered_html disallowed). As a result, an attacker could make a logged in admin update the settings to arbitrary values, and set a Cross-Site Scripting payload in the Message Content. Depending on the options set, the XSS payload can be triggered either in the backend only (in the plugin&amp;#39;s settings), or both frontend and backend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-24535</guid>
    </item>
    <item>
      <title>GHSA-6g8x-82fh-m598</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6g8x-82fh-m598</link>
      <description>&lt;p&gt;The Light Messages WordPress plugin through 1.0 is lacking CSRF check when updating it&amp;#39;s settings, and is not sanitising its Message Content in them (even with the unfiltered_html disallowed). As a result, an attacker could make a logged in admin update the settings to arbitrary values, and set a Cross-Site Scripting payload in the Message Content. Depending on the options set, the XSS payload can be triggered either in the backend only (in the plugin&amp;#39;s settings), or both frontend and backend.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Light Messages WordPress plugin through 1.0 is lacking CSRF check when updating it&amp;#39;s settings, and is not sanitising its Message Content in them (even with the unfiltered_html disallowed). As a result, an attacker could make a logged in admin update the settings to arbitrary values, and set a Cross-Site Scripting payload in the Message Content. Depending on the options set, the XSS payload can be triggered either in the backend only (in the plugin&amp;#39;s settings), or both frontend and backend.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6g8x-82fh-m598</guid>
    </item>
    <item>
      <title>gsd-2021-24535</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-24535</link>
      <description>gsd-2021-24535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-24535</guid>
    </item>
  </channel>
</rss>
