# CVE-2026-33731: AVideo has an Authorize.Net Webhook Signature Bypass that Enables Wallet Balance Inflation via Forged Payment Data

> Attackers can forge webhook signatures to inflate wallet balances and activate premium subscriptions without payment, causing revenue loss.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-95jh-7r58-xmxw

## What is CVE-2026-33731?

CVE-2026-33731 is a medium-severity vulnerability in WWBN AVideo, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. In versions prior to 29.0, the Authorize.Net webhook handler at plugin/AuthorizeNet/webhook.php contains a signature verification bypass that allows an attacker to forge webhook requests with arbitrary payment amounts and target user IDs. By supplying a valid transaction ID from a small legitimate purchase, the attacker bypasses signature validation and credits arbitrary wallet balances to any user account via attacker-controlled payload fields. Three flaws combine into an exploit chain: signature bypass via OR logic (webhook.php:33), payload values override API-fetched values (AuthorizeNet.php:169-171, webhook.php:44-48) and a missing approval check (webhook.php:61-75). By forging payment metadata, an attacker can credit arbitrary amounts to any user's wallet without a corresponding payment and include a  plans_id  to activate premium subscriptions (webhook.php:86-134), enabling free access to all paid and premium content and causing direct revenue loss to the platform owner. This issue has been fixed in version 29.0.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-33731?

2 open source packages ship an affected version, including wwbn/avideo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions | 29.0 |
| `wwbn/avideo` | Packagist | All versions | 29.0 |

## How do I fix CVE-2026-33731?

Upgrade wwbn/avideo to 29.0 or later.

## Is CVE-2026-33731 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33731 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33731 and fix it if it is affected.

What it is: CVE-2026-33731 is a medium-severity vulnerability in WWBN AVideo, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33731 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions; fixed in 29.0
- wwbn/avideo (Packagist): affected all versions; fixed in 29.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33731/ (Markdown: https://insights.sbomify.com/CVE-2026-33731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33731
- OSV: https://osv.dev/vulnerability/CVE-2026-33731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33731/
Summaries are generated and may contain mistakes; the official description above is the record.