<?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 14:27:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-333681</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-333681</link>
      <description>EUVD-2026-333681</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-333681</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53642</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53642</link>
      <description>&lt;p&gt;FOSSBilling is a free, open-source billing and client management system. In versions 0.5.6 through 0.7.2, when the &amp;#34;Require Email Confirmation&amp;#34; setting is enabled, a logged-in client with an unverified email address (`email_approved = 0`) can access all client-area pages (e.g. `/client/balance`, `/client/order/list`, `/client/invoice`) and read real account data, including wallet balances and transaction history. The API-side enforcement correctly restricts unverified clients to only profile-related endpoints, but the page-side enforcement is overly permissive, allowing any request whose path starts with `/client`. Version 0.8.0 contains a fix. No known workarounds that don&amp;#39;t involve modifying the source code are available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FOSSBilling is a free, open-source billing and client management system. In versions 0.5.6 through 0.7.2, when the &amp;#34;Require Email Confirmation&amp;#34; setting is enabled, a logged-in client with an unverified email address (`email_approved = 0`) can access all client-area pages (e.g. `/client/balance`, `/client/order/list`, `/client/invoice`) and read real account data, including wallet balances and transaction history. The API-side enforcement correctly restricts unverified clients to only profile-related endpoints, but the page-side enforcement is overly permissive, allowing any request whose path starts with `/client`. Version 0.8.0 contains a fix. No known workarounds that don&amp;#39;t involve modifying the source code are available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53642</guid>
    </item>
  </channel>
</rss>
