<?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>Fri, 09 Oct 2026 19:23:34 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-292741</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-292741</link>
      <description>EUVD-2026-292741</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-292741</guid>
    </item>
    <item>
      <title>fkie_cve-2026-4121</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-4121</link>
      <description>&lt;p&gt;The Kcaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.1. This is due to missing nonce validation in the plugin&amp;#39;s settings page handler (admin/setting.php). The settings form does not include a wp_nonce_field() and the form processing code does not call wp_verify_nonce() or check_admin_referer() before saving settings to the database via $wpdb-&amp;gt;update(). This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s CAPTCHA settings (enabling or disabling CAPTCHA on login, registration, lost password, and comment forms) via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Kcaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.1. This is due to missing nonce validation in the plugin&amp;#39;s settings page handler (admin/setting.php). The settings form does not include a wp_nonce_field() and the form processing code does not call wp_verify_nonce() or check_admin_referer() before saving settings to the database via $wpdb-&amp;gt;update(). This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s CAPTCHA settings (enabling or disabling CAPTCHA on login, registration, lost password, and comment forms) via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-4121</guid>
    </item>
    <item>
      <title>GHSA-j4g7-gjv8-gvjh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j4g7-gjv8-gvjh</link>
      <description>&lt;p&gt;The Kcaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.1. This is due to missing nonce validation in the plugin&amp;#39;s settings page handler (admin/setting.php). The settings form does not include a wp_nonce_field() and the form processing code does not call wp_verify_nonce() or check_admin_referer() before saving settings to the database via $wpdb-&amp;gt;update(). This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s CAPTCHA settings (enabling or disabling CAPTCHA on login, registration, lost password, and comment forms) via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Kcaptcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 1.0.1. This is due to missing nonce validation in the plugin&amp;#39;s settings page handler (admin/setting.php). The settings form does not include a wp_nonce_field() and the form processing code does not call wp_verify_nonce() or check_admin_referer() before saving settings to the database via $wpdb-&amp;gt;update(). This makes it possible for unauthenticated attackers to modify the plugin&amp;#39;s CAPTCHA settings (enabling or disabling CAPTCHA on login, registration, lost password, and comment forms) via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j4g7-gjv8-gvjh</guid>
    </item>
  </channel>
</rss>
