<?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 11:57:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-218385</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218385</link>
      <description>EUVD-2026-218385</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218385</guid>
    </item>
    <item>
      <title>fkie_cve-2023-0499</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-0499</link>
      <description>&lt;p&gt;The QuickSwish WordPress plugin before 1.1.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The QuickSwish WordPress plugin before 1.1.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-0499</guid>
    </item>
    <item>
      <title>GHSA-hmjg-5c65-5xmj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hmjg-5c65-5xmj</link>
      <description>&lt;p&gt;The QuickSwish WordPress plugin before 1.1.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The QuickSwish WordPress plugin before 1.1.0 does not have CSRF check when activating plugins, which could allow attackers to make logged in admins activate arbitrary plugins present on the blog via a CSRF attack&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hmjg-5c65-5xmj</guid>
    </item>
    <item>
      <title>gsd-2023-0499</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-0499</link>
      <description>gsd-2023-0499</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-0499</guid>
    </item>
  </channel>
</rss>
