<?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>Sun, 25 Oct 2026 23:29:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-12203</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-12203</link>
      <description>EUVD-2026-12203</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-12203</guid>
    </item>
    <item>
      <title>fkie_cve-2022-2171</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-2171</link>
      <description>&lt;p&gt;The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-2171</guid>
    </item>
    <item>
      <title>GHSA-j2wv-pvcq-h7hf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j2wv-pvcq-h7hf</link>
      <description>&lt;p&gt;The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Progressive License WordPress plugin through 1.1.0 is lacking any CSRF check when saving its settings, which could allow attackers to make a logged in admin change them. Furthermore, as the plugin allows arbitrary HTML to be inserted in one of the settings, this could lead to Stored XSS issue which will be triggered in the frontend as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j2wv-pvcq-h7hf</guid>
    </item>
    <item>
      <title>gsd-2022-2171</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-2171</link>
      <description>gsd-2022-2171</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-2171</guid>
    </item>
  </channel>
</rss>
