<?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, 20 Oct 2026 14:41:29 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-286954</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-286954</link>
      <description>EUVD-2026-286954</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-286954</guid>
    </item>
    <item>
      <title>fkie_cve-2024-9821</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-9821</link>
      <description>&lt;p&gt;The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the &amp;#39;stm_wpcfto_get_settings&amp;#39; AJAX action in all versions up to, and including, 1.2.7.  This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the &amp;#39;stm_wpcfto_get_settings&amp;#39; AJAX action in all versions up to, and including, 1.2.7.  This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-9821</guid>
    </item>
    <item>
      <title>GHSA-cfvh-mr6h-3g8q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cfvh-mr6h-3g8q</link>
      <description>&lt;p&gt;The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the &amp;#39;stm_wpcfto_get_settings&amp;#39; AJAX action in all versions up to, and including, 1.2.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to sensitive information disclosure due to missing authorization checks on the &amp;#39;stm_wpcfto_get_settings&amp;#39; AJAX action in all versions up to, and including, 1.2.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to view the Telegram Bot Token, a secret token used to control the bot, which can then be used to log in as any existing user on the site, such as an administrator, if they know the username, due to the Login with Telegram feature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cfvh-mr6h-3g8q</guid>
    </item>
  </channel>
</rss>
