CVE-2026-47696
Undergoing Analysis Undergoing Analysis - In Progress
Arbitrary Wallet Credit in AVideo Plugin

Publication date: 2026-05-29

Last updated on: 2026-05-29

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-29
Last Modified
2026-05-29
Generated
2026-05-29
AI Q&A
2026-05-29
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wwbn avideo to 29.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-345 The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows any authenticated user to arbitrarily add funds to their wallet without proper payment validation, which can lead to unauthorized financial transactions and accounting manipulation.

Such unauthorized financial activities can undermine compliance with standards and regulations that require accurate transaction records and fraud prevention, potentially impacting frameworks like GDPR and HIPAA where data integrity and security are critical.

Specifically, the lack of validation and verification of payment transactions could lead to violations of financial controls and audit requirements mandated by these regulations.


Can you explain this vulnerability to me?

CVE-2026-47696 is a vulnerability in the WWBN AVideo platform affecting versions 29.0 and earlier. It exists in the AuthorizeNet plugin's processPayment.json.php endpoint, which credits a logged-in user's wallet based solely on an attacker-controlled amount parameter sent via POST.

The endpoint does not validate any real payment information such as Authorize.Net transaction IDs, webhook signatures, hosted payment tokens, nonces, or server-side payment records. Instead, it contains a hardcoded success flag and a TODO comment indicating that real payment processing is not implemented.

As a result, any authenticated user can manipulate the amount parameter to add arbitrary funds to their wallet without making a legitimate payment.


How can this vulnerability impact me? :

This vulnerability allows an attacker with a valid user account to inflate their wallet balance arbitrarily by sending crafted requests to the vulnerable endpoint.

  • Unauthorized addition of funds to user wallets.
  • Bypassing monetization controls and payment verification.
  • Potential unauthorized purchases or fund transfers using the inflated wallet balance.
  • Manipulation of accounting records or financial data within the platform.

How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for suspicious POST requests to the endpoint plugin/AuthorizeNet/processPayment.json.php that include manipulated amount parameters. Since the vulnerability allows any logged-in user to add arbitrary funds by sending crafted POST requests, inspecting web server logs or using network monitoring tools to identify unusual or repeated POST requests to this endpoint with varying amount values can help detect exploitation attempts.

A possible command to detect such activity on a Linux server with access logs might be:

  • grep 'POST /plugin/AuthorizeNet/processPayment.json.php' /var/log/apache2/access.log | grep 'amount='

Additionally, monitoring wallet balance changes in the application database for unexpected increases without corresponding verified payment transactions can help identify exploitation.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include disabling or removing the vulnerable endpoint plugin/AuthorizeNet/processPayment.json.php to prevent any unauthorized wallet crediting.

Ensure that wallet credits are only applied after verifying legitimate payment transactions from Authorize.Net, including validating transaction IDs, webhook signatures, hosted payment tokens, nonces, or server-side payment records.

Until a proper patch or update is available, restrict access to the AuthorizeNet and YPTWallet plugins or disable them if they are not essential.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart