<?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>Mon, 12 Oct 2026 18:22:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-23798</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-23798</link>
      <description>EUVD-2026-23798</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-23798</guid>
    </item>
    <item>
      <title>fkie_cve-2021-24328</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-24328</link>
      <description>&lt;p&gt;The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin&amp;#39;s settings to arbitrary values, and set XSS payloads on them as well&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin&amp;#39;s settings to arbitrary values, and set XSS payloads on them as well&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-24328</guid>
    </item>
    <item>
      <title>GHSA-3fcr-4vvp-335p</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3fcr-4vvp-335p</link>
      <description>&lt;p&gt;The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin&amp;#39;s settings to arbitrary values, and set XSS payloads on them as well&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin&amp;#39;s settings to arbitrary values, and set XSS payloads on them as well&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3fcr-4vvp-335p</guid>
    </item>
    <item>
      <title>gsd-2021-24328</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-24328</link>
      <description>gsd-2021-24328</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-24328</guid>
    </item>
  </channel>
</rss>
