<?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, 19 Oct 2026 12:36:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-288018</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-288018</link>
      <description>EUVD-2026-288018</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-288018</guid>
    </item>
    <item>
      <title>fkie_cve-2025-14167</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-14167</link>
      <description>&lt;p&gt;The Remove Post Type Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to incorrect nonce validation logic that uses OR (||) instead of AND (&amp;amp;&amp;amp;), causing the validation to fail when the nonce field is not empty OR when verification fails, rather than when it&amp;#39;s empty AND verification fails. This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s post type slug removal settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Remove Post Type Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to incorrect nonce validation logic that uses OR (||) instead of AND (&amp;amp;&amp;amp;), causing the validation to fail when the nonce field is not empty OR when verification fails, rather than when it&amp;#39;s empty AND verification fails. This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s post type slug removal settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-14167</guid>
    </item>
    <item>
      <title>GHSA-2prm-vrmg-5674</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2prm-vrmg-5674</link>
      <description>&lt;p&gt;The Remove Post Type Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to incorrect nonce validation logic that uses OR (||) instead of AND (&amp;amp;&amp;amp;), causing the validation to fail when the nonce field is not empty OR when verification fails, rather than when it&amp;#39;s empty AND verification fails. This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s post type slug removal settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Remove Post Type Slug plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to incorrect nonce validation logic that uses OR (||) instead of AND (&amp;amp;&amp;amp;), causing the validation to fail when the nonce field is not empty OR when verification fails, rather than when it&amp;#39;s empty AND verification fails. This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s post type slug removal settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2prm-vrmg-5674</guid>
    </item>
  </channel>
</rss>
