CVE-2026-47696: WWBN AVideo Authenticated Wallet Credit Bypass Vulnerability

HIGH
Advisory Identifier: GHSA-9392-pj54-qqf8
CVSS 4.3
CWE-345
Published
Advisory Summary

CVE-2026-47696 is a HIGH (CVSS 4.3) authenticated wallet credit bypass vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting WWBN AVideo libraries in the Packagist ecosystem. The issue involves authenticated wallet credit bypass in authorizenet processpayment endpoint. Remediation is available in the latest vendor maintenance releases.

CVE-2026-47696 at a Glance

CVE Identifier CVE-2026-47696
GHSA Identifier GHSA-9392-pj54-qqf8
Severity HIGH
CVSS v3.1 Base Score 4.3
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product WWBN AVideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-47696

To remediate this vulnerability, upgrade all affected WWBN AVideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

WWBN/AVideo fixed: Latest secure release
Upgrade WWBN/AVideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for WWBN/AVideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-47696, inspect your project dependencies for WWBN AVideo:

inspect dependencies for WWBN/AVideo

Analyze the terminal output to locate any version of WWBN AVideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In WWBN AVideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 json_encode(['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; $users_id = @User::getId(); if ($paymentSuccess && !empty($users_id)) { $walletPlugin = AVideoPlugin::loadPluginIfEnabled("YPTWallet"); if ($walletPlugin) { $walletPlugin->addBalance($users_id, $amount, 'Authorize.Net one-time payment'); echo json_encode(['success' => true, 'result' => 'Payment processed and wallet updated']); exit; } } ``` Vulnerable flow: 1. `$_POST['amount']` is read from the client. 2. The endpoint only checks that the amount is greater than zero. 3. The real Authorize.Net charge is not performed. 4. `$paymentSuccess` is hardcoded to true. 5. The logged-in user's wallet is credited with the client-supplied amount. There is no verification of: - Authorize.Net transaction ID - payment token - webhook signature - pending payment record - expected server-side amount - currency - duplicate transaction/replay state ### PoC Prerequisites: - AVideo with AuthorizeNet plugin enabled - YPTWallet plugin enabled - Attacker has any valid user account Steps: 1. Log in as a low-privileged user. 2. Open the wallet page and record the current balance. 3. Send the following request with the user's authenticated session cookie: ``` curl -i -s -b 'PHPSESSID=<user_session>' \ -X POST 'https://target.example/plugin/AuthorizeNet/processPayment.json.php' \ --data 'amount=9999&userData[note]=poc' ``` 4. The endpoint returns: ``` {"success":true,"result":"Payment processed and wallet updated"} ``` 5. Refresh the wallet page. 6. 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 Affected WWBN AVideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
WWBN/AVideo
Packagist
≤ 29.0

References

Frequently Asked Questions

What is CVE-2026-47696?
CVE-2026-47696 is a security vulnerability in WWBN AVideo involving Authenticated wallet credit bypass in AuthorizeNet processPayment endpoint under CWE-345: Insufficient Verification of Data Authenticity.
Which WWBN AVideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: WWBN/AVideo.
What version fixes CVE-2026-47696?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is WWBN/AVideo affected?
Yes, WWBN/AVideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-47696?
CVE-2026-47696 has a CVSS v3.1 base score of 4.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-47696?
CVE-2026-47696 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Packagist dependencies for CVE-2026-47696?
Run the dependency tree command: 'inspect dependencies for WWBN/AVideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9392-pj54-qqf8",
  "modified" : "2026-06-04T18:47:35Z",
  "published" : "2026-06-04T18:47:35Z",
  "aliases" : [ "CVE-2026-47696" ],
  "summary" : "WWBN AVideo: Authenticated wallet credit bypass in AuthorizeNet processPayment endpoint",
  "details" : "### Summary\n\n  `plugin/AuthorizeNet/processPayment.json.php` credits the logged-in user's wallet based only on the attacker-controlled `amount` POST parameter.\n\n  The endpoint contains a TODO for real Authorize.Net charging, hardcodes `$paymentSuccess = true`, and then calls `YPTWallet::addBalance()` without validating\n  any Authorize.Net transaction, webhook signature, hosted payment token, nonce, or server-side payment record.\n\n  This allows any logged-in user to add arbitrary funds to their own AVideo wallet when the `AuthorizeNet` and `YPTWallet` plugins are enabled.\n\n  ### Details\n\n  Affected file:\n\n  `plugin/AuthorizeNet/processPayment.json.php`\n\n  Relevant code:\n\n  ```php\n  $amount = isset($_POST['amount']) ? floatval($_POST['amount']) : 0;\n  $userData = isset($_POST['userData']) ? $_POST['userData'] : [];\n\n  if ($amount <= 0) {\n      echo json_encode(['error' => 'Invalid amount']);\n      exit;\n  }\n\n  // TODO: Implement payment logic using Authorize.Net API\n  // Example: Call Authorize.Net API here\n  // $result = $plugin->chargePayment($amount, $userData);\n\n  // Simulate payment success for now\n  $paymentSuccess = true;\n  $users_id = @User::getId();\n\n  if ($paymentSuccess && !empty($users_id)) {\n      $walletPlugin = AVideoPlugin::loadPluginIfEnabled(\"YPTWallet\");\n      if ($walletPlugin) {\n          $walletPlugin->addBalance($users_id, $amount, 'Authorize.Net one-time payment');\n          echo json_encode(['success' => true, 'result' => 'Payment processed and wallet updated']);\n          exit;\n      }\n  }\n```\n  Vulnerable flow:\n\n  1. `$_POST['amount']` is read from the client.\n  2. The endpoint only checks that the amount is greater than zero.\n  3. The real Authorize.Net charge is not performed.\n  4. `$paymentSuccess` is hardcoded to true.\n  5. The logged-in user's wallet is credited with the client-supplied amount.\n\n  There is no verification of:\n\n  - Authorize.Net transaction ID\n  - payment token\n  - webhook signature\n  - pending payment record\n  - expected server-side amount\n  - currency\n  - duplicate transaction/replay state\n\n  ### PoC\n\n  Prerequisites:\n\n  - AVideo with AuthorizeNet plugin enabled\n  - YPTWallet plugin enabled\n  - Attacker has any valid user account\n\n  Steps:\n\n  1. Log in as a low-privileged user.\n  2. Open the wallet page and record the current balance.\n  3. Send the following request with the user's authenticated session cookie:\n```\n  curl -i -s -b 'PHPSESSID=<user_session>' \\\n    -X POST 'https://target.example/plugin/AuthorizeNet/processPayment.json.php' \\\n    --data 'amount=9999&userData[note]=poc'\n```\n  4. The endpoint returns:\n```\n  {\"success\":true,\"result\":\"Payment processed and wallet updated\"}\n```\n  5. Refresh the wallet page.\n  6. The wallet balance is increased by 9999.\n\n  No Authorize.Net hosted payment page, card payment, transaction confirmation, webhook, or server-side payment validation is required.\n\n### Impact\n\n  A normal authenticated user can mint arbitrary wallet balance.\n\n  Depending on the target site's configuration, this may allow the attacker to:\n\n  - purchase paid videos or subscriptions without payment\n  - abuse any feature backed by YPTWallet\n  - transfer fake funds to other users\n  - manipulate accounting or payout-related workflows\n  - bypass monetization controls\n\n### Recommended fix\n\n- Remove or disable `processPayment.json.php` if it is obsolete.\n- Never credit wallet balance from client-supplied `amount` alone.\n- Use the existing Authorize.Net hosted token / webhook / transaction reconciliation flow.\n- Require a verified Authorize.Net transaction ID and server-side amount lookup before calling `addBalance()`.\n- Add regression tests proving arbitrary POSTs cannot credit a wallet.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "WWBN/AVideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "29.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-9392-pj54-qqf8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47696"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/822402444b4db4e9442779c8c789ffe5312b3627"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-04T18:47:35Z",
    "nvd_published_at" : "2026-05-29T14:16:32Z"
  }
}