<?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>Sun, 18 Oct 2026 21:49:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-11760 — eRoom – Webinar &amp; Meeting Plugin for Zoom, Google Meet, Microsoft Teams &lt;= 1.5.6 - Unauthenticated Sensitive Informatio…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-11760</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; digitalmeactivecampaign eRoom – Webinar &amp;amp; Meeting Plugin for Zoom, Google Meet, Microsoft Teams&lt;/p&gt;
&lt;p&gt;The eRoom – Webinar &amp;amp; Meeting Plugin for Zoom, Google Meet, Microsoft Teams plugin for WordPress is vulnerable to exposure of sensitive information in all versions up to, and including, 1.5.6. This is due to the plugin exposing Zoom SDK secret keys in client-side JavaScript within the meeting view template. This makes it possible for unauthenticated attackers to extract the sdk_secret value, which should remain server-side, compromising the security of the Zoom integration and allowing attackers to generate valid JWT signatures for unauthorized meeting access.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; digitalmeactivecampaign eRoom – Webinar &amp;amp; Meeting Plugin for Zoom, Google Meet, Microsoft Teams&lt;/p&gt;
&lt;p&gt;The eRoom – Webinar &amp;amp; Meeting Plugin for Zoom, Google Meet, Microsoft Teams plugin for WordPress is vulnerable to exposure of sensitive information in all versions up to, and including, 1.5.6. This is due to the plugin exposing Zoom SDK secret keys in client-side JavaScript within the meeting view template. This makes it possible for unauthenticated attackers to extract the sdk_secret value, which should remain server-side, compromising the security of the Zoom integration and allowing attackers to generate valid JWT signatures for unauthorized meeting access.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-11760</guid>
    </item>
  </channel>
</rss>
