Quick answers
- Is CVE-2026-47696 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47696 being exploited in the wild.
- How severe is CVE-2026-47696?
- Medium severity, with a CVSS score of 4.3, published 29 May 2026.
- Which products and versions are affected?
- wwbn/avideo (Packagist) <= 29.0, ECOSYSTEM:introduced=0,last_affected=29.0; WWBN AVideo <= 29.0, 29.0 and earlier.
- Is there a fix for CVE-2026-47696?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47696 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47696?
- Check whether you run wwbn/avideo (Packagist) or WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in `plugin/AuthorizeNet/processPayment.json.php` where the application fails to verify payment authenticity. The code contains a 'TODO' for actual API implementation and instead hardcodes the `$paymentSuccess` variable to `true`. An attacker can send a POST request to this endpoint with an arbitrary `amount` parameter; the system then calls `YPTWallet::addBalance()` to credit the user's account without validating transaction IDs, webhook signatures, or server-side records. This requires the AuthorizeNet and YPTWallet plugins to be enabled and the attacker to have a valid user session.
Affected products
- WWBN AVideo <= 29.0
Identifiers
- CVE-2026-47696
- GHSA-9392-pj54-qqf8
Timeline
- 2026-05-19: disclosed: Advisory published by reporter
- 2026-05-29: advisory: NVD publication date
- 2026-06-04: advisory: GitHub Advisory Database publication date