<?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 18:19:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291813</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291813</link>
      <description>EUVD-2026-291813</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291813</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40308</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40308</link>
      <description>&lt;p&gt;My Calendar is a WordPress plugin for managing calendar events. In versions 3.7.6 and below, the mc_ajax_mcjs_action AJAX endpoint, registered for unauthenticated users, passes user-supplied arguments through parse_str() without validation, allowing injection of arbitrary parameters including a site value. On WordPress Multisite installations, this enables an unauthenticated attacker to call switch_to_blog() with an arbitrary site ID and extract calendar events from any sub-site on the network, including private or hidden events. On standard Single Site installations, switch_to_blog() does not exist, causing an uncaught PHP fatal error and crashing the worker thread, creating an unauthenticated denial of service vector. This issue has been fixed in version 3.7.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;My Calendar is a WordPress plugin for managing calendar events. In versions 3.7.6 and below, the mc_ajax_mcjs_action AJAX endpoint, registered for unauthenticated users, passes user-supplied arguments through parse_str() without validation, allowing injection of arbitrary parameters including a site value. On WordPress Multisite installations, this enables an unauthenticated attacker to call switch_to_blog() with an arbitrary site ID and extract calendar events from any sub-site on the network, including private or hidden events. On standard Single Site installations, switch_to_blog() does not exist, causing an uncaught PHP fatal error and crashing the worker thread, creating an unauthenticated denial of service vector. This issue has been fixed in version 3.7.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40308</guid>
    </item>
    <item>
      <title>GHSA-2mvx-f5qm-v2ch — Unauthenticated Information Disclosure (IDOR) via Multisite switch_to_blog in My Calendar</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2mvx-f5qm-v2ch</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: joedolson/my-calendar&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An unauthenticated Insecure Direct Object Reference (IDOR) and Denial of Service (DoS) vulnerability in the My Calendar plugin allows any unauthenticated user to extract calendar events (including private or hidden ones) from any sub-site on a WordPress Multisite network. On standard Single Site WordPress installations, this same endpoint crashes the PHP worker thread, creating an unauthenticated Denial of Service (DoS) vector.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability stems from the `mc_ajax_mcjs_action AJAX` function, which handles the `mcjs_action` endpoint. This endpoint is explicitly registered for unauthenticated users:
```php
&amp;lt;?php
// In my-calendar-ajax.php
add_action( &amp;#39;wp_ajax_nopriv_mcjs_action&amp;#39;, &amp;#39;mc_ajax_mcjs_action&amp;#39; );
```&lt;/p&gt;
&lt;p&gt;When the behavior parameter is set to loadupcoming, the plugin accepts an args parameter from the $_REQUEST array. Instead of validating specific expected arguments, the plugin unsafely passes the entire string into PHP&amp;#39;s parse_str() function:
```php
&amp;lt;?php
$request = isset( $_REQUEST[&amp;#39;args&amp;#39;] ) ? wp_unslash( sanitize_text_field( $_REQUEST[&amp;#39;args&amp;#39;] ) ) : array();
$request = str_replace( &amp;#39;|&amp;#39;, &amp;#39;&amp;amp;&amp;#39;, $request );
$request = parse_str( $request, $args );
// ...
$response = my_calendar_upcoming_events( $args );
```&lt;/p&gt;
&lt;p&gt;This allows an attacker to inject arbitrary key-value pairs into the $args array. This array is then passed to the my_calendar_upcoming_events() function located in my-calendar-widgets.php.&lt;/p&gt;
&lt;p&gt;At the beginning of this function, the plugin p…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: joedolson/my-calendar&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An unauthenticated Insecure Direct Object Reference (IDOR) and Denial of Service (DoS) vulnerability in the My Calendar plugin allows any unauthenticated user to extract calendar events (including private or hidden ones) from any sub-site on a WordPress Multisite network. On standard Single Site WordPress installations, this same endpoint crashes the PHP worker thread, creating an unauthenticated Denial of Service (DoS) vector.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability stems from the `mc_ajax_mcjs_action AJAX` function, which handles the `mcjs_action` endpoint. This endpoint is explicitly registered for unauthenticated users:
```php
&amp;lt;?php
// In my-calendar-ajax.php
add_action( &amp;#39;wp_ajax_nopriv_mcjs_action&amp;#39;, &amp;#39;mc_ajax_mcjs_action&amp;#39; );
```&lt;/p&gt;
&lt;p&gt;When the behavior parameter is set to loadupcoming, the plugin accepts an args parameter from the $_REQUEST array. Instead of validating specific expected arguments, the plugin unsafely passes the entire string into PHP&amp;#39;s parse_str() function:
```php
&amp;lt;?php
$request = isset( $_REQUEST[&amp;#39;args&amp;#39;] ) ? wp_unslash( sanitize_text_field( $_REQUEST[&amp;#39;args&amp;#39;] ) ) : array();
$request = str_replace( &amp;#39;|&amp;#39;, &amp;#39;&amp;amp;&amp;#39;, $request );
$request = parse_str( $request, $args );
// ...
$response = my_calendar_upcoming_events( $args );
```&lt;/p&gt;
&lt;p&gt;This allows an attacker to inject arbitrary key-value pairs into the $args array. This array is then passed to the my_calendar_upcoming_events() function located in my-calendar-widgets.php.&lt;/p&gt;
&lt;p&gt;At the beginning of this function, the plugin p…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2mvx-f5qm-v2ch</guid>
    </item>
  </channel>
</rss>
