<?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 04:29:07 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-340622</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-340622</link>
      <description>EUVD-2026-340622</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-340622</guid>
    </item>
    <item>
      <title>fkie_cve-2026-15212</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-15212</link>
      <description>&lt;p&gt;The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option &amp;#39;enable_nonce_check&amp;#39;, which is absent from the default &amp;#39;wpo365_options&amp;#39; array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied &amp;#39;settings&amp;#39; payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to &amp;#39;administrator&amp;#39; — 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 WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option &amp;#39;enable_nonce_check&amp;#39;, which is absent from the default &amp;#39;wpo365_options&amp;#39; array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied &amp;#39;settings&amp;#39; payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to &amp;#39;administrator&amp;#39; — 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-2026-15212</guid>
    </item>
    <item>
      <title>GHSA-4w3q-g484-rj57</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4w3q-g484-rj57</link>
      <description>&lt;p&gt;The WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option &amp;#39;enable_nonce_check&amp;#39;, which is absent from the default &amp;#39;wpo365_options&amp;#39; array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied &amp;#39;settings&amp;#39; payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to &amp;#39;administrator&amp;#39; — 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 WPO365 | Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 43.2. This is due to the Ajax_Service::verify_ajax_request() helper gating its wp_verify_nonce() call behind the boolean option &amp;#39;enable_nonce_check&amp;#39;, which is absent from the default &amp;#39;wpo365_options&amp;#39; array and therefore evaluates to false via get_global_boolean_var(); as a result, the wp_ajax_wpo365_update_settings handler (Ajax_Service::update_settings) accepts POSTs from cross-origin pages and forwards the attacker-supplied &amp;#39;settings&amp;#39; payload (base64/JSON) to Options_Service::update_options(), which merges every key/value into wpo365_options without a key allowlist. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin options — including enabling the SCIM REST endpoint (enable_scim), planting an attacker-known scim_secret_token, and setting new_usr_default_role to &amp;#39;administrator&amp;#39; — 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-4w3q-g484-rj57</guid>
    </item>
  </channel>
</rss>
