CVE-2026-33483 | WWBN AVideo up to 26.0 aVideoEncoderChunk.json.php allocation of resources

VDB-352524 · CVE-2026-33483 · GCVE-0-2026-33483 WWBN AVIDEO UP TO 26.0 AVIDEOENCODERCHUNK.JSON.PHP ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.3 $0-$5k 2.50+ Summaryinfo A vulnerability was found in WWBN AVideo up to 26.0 and classified as problematic. The impacted element is an unknown function of the file aVideoEncoderChunk.json.php. The manipulation results in allocation of resources. This vulnerability is cataloged as CVE-2026-33483. The attack may be launched remotely. There is no exploit available. It is advisable to implement a patch to correct this issue. Detailsinfo A vulnerability, which was classified as problematic, was found in WWBN AVideo up to 26.0. Affected is an unknown code of the file aVideoEncoderChunk.json.php. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. CVE summarizes: WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `aVideoEncoderChunk.json.php` endpoint is a completely standalone PHP script with no authentication, no framework includes, and no resource limits. An unauthenticated remote attacker can send arbitrary POST data which is written to persistent temp files in `/tmp/` with no size cap, no rate limiting, and no cleanup mechanism. This allows trivial disk space exhaustion leading to denial of service of the entire server. Commit 33d1bae6c731ef1682fcdc47b428313be073a5d1 contains a patch. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-33483 since 03/20/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1499. By approaching the search of inurl:aVideoEncoderChunk.json.php it is possible to find vulnerable targets with Google Hacking. Applying the patch 33d1bae6c731ef1682fcdc47b428313be073a5d1 is able to eliminate this problem. Productinfo Vendor WWBN Name AVideo Version 26.0 License open-source Website Product: https://github.com/WWBN/AVideo/ CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.4 VulDB Meta Temp Score: 6.3 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Google Hack: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Patch Status: 🔍 0-Day Time: 🔒 Patch: 33d1bae6c731ef1682fcdc47b428313be073a5d1 Timelineinfo 03/20/2026 CVE reserved 03/23/2026 +3 days Advisory disclosed 03/23/2026 +0 days VulDB entry created 03/23/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33483 (🔒) GCVE (CVE): GCVE-0-2026-33483 GCVE (VulDB): GCVE-100-352524 Entryinfo Created: 03/23/2026 15:39 Changes: 03/23/2026 15:39 (63) Complete: 🔍 Cache ID: 99:387:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸