CVE-2026-47696 is a high-severity security vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
Summary 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. ### Details Affected file: plugin/AuthorizeNet/processPayment.json.php Relevant code: php $amount = isset($POST['amount']) ? floatval($POST['amount']) : 0; $userData = isset($POST['userData']) ? $POST['userData'] : []; if ($amount <= 0) { echo jsonencode(['error' => 'Invalid amount']); exit; } // TODO: Implement payment logic using Authorize.Net API // Example: Call Authorize.Net API here // $result = $plugin->chargePayment($amount, $userData); // Simulate payment success for now $paymentSuccess = true; $usersid = @User::getId(); if ($paymentSuccess && !empty($usersid)) { $walletPlugin = AVideoPlugin::loadPluginIfEnabled("YPTWallet"); if ($walletPlugin) { $walletPlugin->addBalance($usersid, $amount, 'Authorize.Net one-time payment'); echo jsonencode(['success' => true, 'result' => 'Payment processed and wallet updated']); exit; } } curl -i -s -b 'PHPSESSID=<usersession>' \ -X POST 'https://target.example/plugin/AuthorizeNet/processPayment.json.php' \ --data 'amount=9999&userData[note]=poc' {"success":true,"result":"Payment processed and wallet updated"} Refresh the wallet page. The wallet balance is increased by 9999. No Authorize.Net hosted payment page, card payment, transaction confirmation, webhook, or server-side payment validation is required. Impact A normal authenticated user can mint arbitrary wallet balance. Depending on the target site's configuration, this may allow the attacker to: purchase paid videos or subscriptions without payment abuse any feature backed by YPTWallet transfer fake funds to other users manipulate accounting or payout-related workflows bypass monetization controls Recommended fix Remove or disable processPayment.json.php if it is obsolete. Never credit wallet balance from client-supplied amount alone. Use the existing Authorize.Net hosted token / webhook / transaction reconciliation flow. Require a verified Authorize.Net transaction ID and server-side amount lookup before calling addBalance(). Add regression tests proving arbitrary POSTs cannot credit a wallet.
CVE-2026-47696 has a CVSS score of 4.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
composer
WWBN/AVideo (<= 29.0)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-47696 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-47696 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-47696 in your environment →No fixed version is listed for CVE-2026-47696 yet.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-47696 is a high-severity security vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
CVE-2026-47696 has a CVSS score of 4.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
WWBN/AVideo (composer) versions <= 29.0 is affected.
No fixed version is listed for CVE-2026-47696 yet. Monitor the advisory for updates and apply mitigations in the interim.
Whether CVE-2026-47696 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.