Summary
WWBN AVideo: Authenticated wallet credit bypass in AuthorizeNet processPayment endpoint
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
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.
Affected versions
Security releases
Kodem intelligence
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Remove or disable
processPayment.json.phpif it is obsolete. - Never credit wallet balance from client-supplied
amountalone. - 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.
Frequently Asked Questions
- What is CVE-2026-47696? CVE-2026-47696 is a high-severity security vulnerability in WWBN/AVideo (composer), affecting versions <= 29.0. No fixed version is listed yet.
- How severe is CVE-2026-47696? 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.
- Which versions of WWBN/AVideo are affected by CVE-2026-47696? WWBN/AVideo (composer) versions <= 29.0 is affected.
- Is there a fix for CVE-2026-47696? No fixed version is listed for CVE-2026-47696 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-47696 exploitable, and should I be worried? 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
- What actually determines whether CVE-2026-47696 is exploitable, and how bad it is? 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.