Quick answers
- Is CVE-2026-33684 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33684 being exploited in the wild.
- How severe is CVE-2026-33684?
- Medium severity, with a CVSS score of 5.3, published 15 July 2026.
- Which products and versions are affected?
- wwbn/avideo (Packagist) < 29.0, ECOSYSTEM:introduced=0,fixed=29.0; WWBN AVideo < 29.0.
- Is there a fix for CVE-2026-33684?
- 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-33684 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-33684?
- 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
A privilege escalation vulnerability exists in the `set_api_signUp` method within the API plugin of WWBN AVideo. The root cause is a failure to validate the `APISecret` before processing sensitive parameters such as `emailVerified`, `canUpload`, `canStream`, and `canCreateMeet`. While the code checks for either a valid `APISecret` or a solved CAPTCHA to allow registration, it fails to restrict the subsequent permission-setting logic to only those requests authenticated with the secret. An unauthenticated remote attacker can solve a CAPTCHA and submit a crafted POST request to `set.json.php` to register an account with elevated privileges. This allows attackers to bypass email verification and administrative restrictions on uploading or streaming. The issue is resolved in version 29.0.
Affected products
- WWBN AVideo < 29.0
Identifiers
- CVE-2026-33684
- GHSA-8j8m-p79x-g4jm
Timeline
- 2026-06-22: advisory: GitHub advisory published by maintainer
- 2026-07-15: disclosed: NVD publication date
- 2026-07-15: patched: Fixed in version 29.0