Is CVE-2026-33731 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33731 being exploited in the wild.

How severe is CVE-2026-33731?

Medium severity, with a CVSS score of 6.5, published 16 July 2026.

Which products and versions are affected?

wwbn/avideo (Packagist) <= 28.0, ECOSYSTEM:introduced=0,fixed=29.0; WWBN AVideo < 29.0, <= 28.0.

Is there a fix for CVE-2026-33731?

Yes. wwbn/avideo (Packagist): upgrade to 29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33731 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-33731?

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.

CVE-2026-33731: WWBN AVideo signature verification bypass in Authorize.Net webhook

Q: Is there a fix for CVE-2026-33731?

Yes. wwbn/avideo (Packagist): upgrade to 29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-33731 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-33731?

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.

CVE-2026-33731 · Severity: medium · CVSS 6.5 · Published 2026-07-16

WWBN AVideo is an open-source video sharing platform. A vulnerability in its payment processing system allows users to bypass security checks when using the Authorize.Net payment gateway. By manipulating payment notifications, an attacker can falsely credit their account with any amount of money or activate premium subscriptions without actually paying. This results in direct financial loss for the platform owner and unauthorized access to paid content.

Technologies: wwbn/avideo (Packagist), WWBN AVideo. Vendors: Packagist, WWBN.

Quick answers

Is CVE-2026-33731 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33731 being exploited in the wild.
How severe is CVE-2026-33731?: Medium severity, with a CVSS score of 6.5, published 16 July 2026.
Which products and versions are affected?: wwbn/avideo (Packagist) <= 28.0, ECOSYSTEM:introduced=0,fixed=29.0; WWBN AVideo < 29.0, <= 28.0.
Is there a fix for CVE-2026-33731?: Yes. wwbn/avideo (Packagist): upgrade to 29.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33731 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-33731?: 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.

How to fix

wwbn/avideo (Packagist): upgrade to 29.0 or later
```
composer require wwbn/avideo:^29.0
```

Technical details

The Authorize.Net webhook handler in `plugin/AuthorizeNet/webhook.php` contains a logic error in its signature validation. Specifically, an 'OR' condition allows execution to continue if a valid transaction ID is provided, even if the cryptographic signature is missing or invalid. By using a transaction ID from a legitimate small purchase, an attacker can submit a forged JSON payload where the 'amount' and 'users_id' fields override the actual transaction data fetched from the API. Furthermore, the application fails to verify the 'isApproved' status before calling `processSinglePayment()`. This exploit chain allows a low-privileged user to credit arbitrary funds to any account or activate premium plans by including a 'plans_id' in the forged metadata. The issue is fixed in version 29.0.

Affected products

WWBN AVideo < 29.0

Identifiers

CVE-2026-33731
GHSA-95jh-7r58-xmxw

Timeline

2026-03-23: patched: Fix committed to repository
2026-06-22: advisory: GitHub Security Advisory published
2026-07-16: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.