<?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, 20 Oct 2026 03:39:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213447</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213447</link>
      <description>EUVD-2026-213447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213447</guid>
    </item>
    <item>
      <title>fkie_cve-2023-0420</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-0420</link>
      <description>&lt;p&gt;The Custom Post Type and Taxonomy GUI Manager WordPress plugin through 1.1 does not have CSRF, and is lacking sanitising as well as escaping in some parameters, allowing attackers to make a logged in admin put Stored Cross-Site Scripting payloads via CSRF&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Custom Post Type and Taxonomy GUI Manager WordPress plugin through 1.1 does not have CSRF, and is lacking sanitising as well as escaping in some parameters, allowing attackers to make a logged in admin put Stored Cross-Site Scripting payloads via CSRF&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-0420</guid>
    </item>
    <item>
      <title>GHSA-qrm5-6xmw-6xcq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qrm5-6xmw-6xcq</link>
      <description>&lt;p&gt;The Custom Post Type and Taxonomy GUI Manager WordPress plugin through 1.1 does not have CSRF, and is lacking sanitising as well as escaping in some parameters, allowing attackers to make a logged in admin put Stored Cross-Site Scripting payloads via CSRF&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Custom Post Type and Taxonomy GUI Manager WordPress plugin through 1.1 does not have CSRF, and is lacking sanitising as well as escaping in some parameters, allowing attackers to make a logged in admin put Stored Cross-Site Scripting payloads via CSRF&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qrm5-6xmw-6xcq</guid>
    </item>
    <item>
      <title>gsd-2023-0420</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-0420</link>
      <description>gsd-2023-0420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-0420</guid>
    </item>
  </channel>
</rss>
