<?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>Mon, 19 Oct 2026 11:37:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281056</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281056</link>
      <description>EUVD-2026-281056</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281056</guid>
    </item>
    <item>
      <title>fkie_cve-2026-35448</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-35448</link>
      <description>&lt;p&gt;WWBN AVideo is an open source video platform. In versions 26.0 and prior, the BlockonomicsYPT plugin&amp;#39;s check.php endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated invoice.php page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;WWBN AVideo is an open source video platform. In versions 26.0 and prior, the BlockonomicsYPT plugin&amp;#39;s check.php endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated invoice.php page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-35448</guid>
    </item>
    <item>
      <title>GHSA-3v7m-qg4x-58h9 — AVideo: Unauthenticated Access to Payment Order Data via BlockonomicsYPT check.php</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3v7m-qg4x-58h9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wwbn/avideo&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The BlockonomicsYPT plugin&amp;#39;s `check.php` endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated `invoice.php` page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;In `plugin/BlockonomicsYPT/check.php` at lines 20-30, the endpoint accepts a Bitcoin address and returns the corresponding order data:&lt;/p&gt;
&lt;p&gt;```php
$addr = $_GET[&amp;#39;addr&amp;#39;];
$order = new BlockonomicsOrder(0);
$obj = $order-&amp;gt;getFromAddressFromDb($addr);
die(json_encode($obj));
```&lt;/p&gt;
&lt;p&gt;There is no authentication check. The endpoint does not verify that the requesting user is logged in, nor does it verify that the requesting user owns the order associated with the given address.&lt;/p&gt;
&lt;p&gt;The response includes:
- User ID of the buyer
- Total payment value
- Currency
- BTC amounts (expected and received)
- Transaction ID
- Payment status&lt;/p&gt;
&lt;p&gt;The `invoice.php` page that was designed to consume this endpoint does require authentication, but `check.php` itself does not inherit or enforce that requirement.&lt;/p&gt;
&lt;p&gt;Bitcoin addresses are publicly queryable on the blockchain, so an attacker does not need to guess them. Addresses associated with the platform can be discovered by monitoring blockchain transactions to known platform wallets.&lt;/p&gt;
&lt;p&gt;The BlockonomicsYPT plugin is tagged…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: wwbn/avideo&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The BlockonomicsYPT plugin&amp;#39;s `check.php` endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated `invoice.php` page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;In `plugin/BlockonomicsYPT/check.php` at lines 20-30, the endpoint accepts a Bitcoin address and returns the corresponding order data:&lt;/p&gt;
&lt;p&gt;```php
$addr = $_GET[&amp;#39;addr&amp;#39;];
$order = new BlockonomicsOrder(0);
$obj = $order-&amp;gt;getFromAddressFromDb($addr);
die(json_encode($obj));
```&lt;/p&gt;
&lt;p&gt;There is no authentication check. The endpoint does not verify that the requesting user is logged in, nor does it verify that the requesting user owns the order associated with the given address.&lt;/p&gt;
&lt;p&gt;The response includes:
- User ID of the buyer
- Total payment value
- Currency
- BTC amounts (expected and received)
- Transaction ID
- Payment status&lt;/p&gt;
&lt;p&gt;The `invoice.php` page that was designed to consume this endpoint does require authentication, but `check.php` itself does not inherit or enforce that requirement.&lt;/p&gt;
&lt;p&gt;Bitcoin addresses are publicly queryable on the blockchain, so an attacker does not need to guess them. Addresses associated with the platform can be discovered by monitoring blockchain transactions to known platform wallets.&lt;/p&gt;
&lt;p&gt;The BlockonomicsYPT plugin is tagged…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3v7m-qg4x-58h9</guid>
    </item>
  </channel>
</rss>
