<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T19:09:34.622943+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-322763</id>
    <title>EUVD-2026-322763</title>
    <updated>2026-10-10T19:09:34.680598+00:00</updated>
    <content>EUVD-2026-322763</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-322763"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47696</id>
    <title>fkie_cve-2026-47696</title>
    <updated>2026-10-10T19:09:34.680647+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WWBN AVideo is an open source video platform. In 29.0 and earlier, plugin/AuthorizeNet/processPayment.json.php credits the logged-in user's wallet based only on the attacker-controlled amount POST parameter. The endpoint contains a TODO for real Authorize.Net charging, hardcodes $paymentSuccess = true, and then calls YPTWallet::addBalance() without validating
any Authorize.Net transaction, webhook signature, hosted payment token, nonce, or server-side payment record. This allows any logged-in user to add arbitrary funds to their own AVideo wallet when the AuthorizeNet and YPTWallet plugins are enabled.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-47696"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9392-pj54-qqf8</id>
    <title>GHSA-9392-pj54-qqf8 — WWBN AVideo: Authenticated wallet credit bypass in AuthorizeNet processPayment endpoint</title>
    <updated>2026-10-10T19:09:34.680703+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: WWBN/AVideo</p>
<p>### Summary</p>
<p>`plugin/AuthorizeNet/processPayment.json.php` credits the logged-in user's wallet based only on the attacker-controlled `amount` POST parameter.</p>
<p>The endpoint contains a TODO for real Authorize.Net charging, hardcodes `$paymentSuccess = true`, and then calls `YPTWallet::addBalance()` without validating
  any Authorize.Net transaction, webhook signature, hosted payment token, nonce, or server-side payment record.</p>
<p>This allows any logged-in user to add arbitrary funds to their own AVideo wallet when the `AuthorizeNet` and `YPTWallet` plugins are enabled.</p>
<p>### Details</p>
<p>Affected file:</p>
<p>`plugin/AuthorizeNet/processPayment.json.php`</p>
<p>Relevant code:</p>
<p>```php
  $amount = isset($_POST['amount']) ? floatval($_POST['amount']) : 0;
  $userData = isset($_POST['userData']) ? $_POST['userData'] : [];</p>
<p>if ($amount &lt;= 0) {
      echo json_encode(['error' =&gt; 'Invalid amount']);
      exit;
  }</p>
<p>// TODO: Implement payment logic using Authorize.Net API
  // Example: Call Authorize.Net API here
  // $result = $plugin-&gt;chargePayment($amount, $userData);</p>
<p>// Simulate payment success for now
  $paymentSuccess = true;
  $users_id = @User::getId();</p>
<p>if ($paymentSuccess &amp;&amp; !empty($users_id)) {
      $walletPlugin = AVideoPlugin::loadPluginIfEnabled("YPTWallet");
      if ($walletPlugin) {
          $walletPlugin-&gt;addBalance($users_id, $amount, 'Authorize.Net one-time payment');
          echo json_encode(['success' =&gt; true, 'result' =&gt; 'Payment processed and wallet…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9392-pj54-qqf8"/>
  </entry>
</feed>
