CVE-2026-33037: WWBN AVideo · Insecure Default Initialization of Resource
Affects WWBN AVideoSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 26.0 soon.
Data as of 1 Nov 2026, 11:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade AVideo and wwbn/AVideo to 26.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WWBNAVideo | Affected
| Fixed in
|
GitHubwwbn/AVideopkg:github/wwbn/AVideoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, organizations should immediately upgrade to WWBN AVideo version 26.0 or later, where the issue is fixed. For existing deployments, it is critical to override the SYSTEM_ADMIN_PASSWORD environment variable during installation with a strong, unique password and ensure the database credentials are also changed from their defaults. Implement a policy to enforce password complexity and mandate password changes on first login to prevent default password usage. Additionally, replace the weak MD5 password hashing with a modern, secure hashing algorithm such as bcrypt or Argon2. Conduct thorough audits of all AVideo instances, especially those deployed via Docker, to detect and remediate any instances still using default credentials. Restrict access to the Docker deployment files and environment variables to trusted administrators only. Monitor logs and user activity for signs of unauthorized access or exploitation attempts. Consider implementing network segmentation and application-layer firewalls to limit exposure of the AVideo platform to untrusted networks.
Description
WWBN AVideo is an open source video platform. In versions 25.0 and below, the official Docker deployment files (docker-compose.yml, env.example) ship with the admin password set to "password", which is automatically used to seed the admin account during installation, meaning any instance deployed without overriding SYSTEM_ADMIN_PASSWORD is immediately vulnerable to trivial administrative takeover. No compensating controls exist: there is no forced password change on first login, no complexity validation, no default-password detection, and the password is hashed with weak MD5. Full admin access enables user data exposure, content manipulation, and potential remote code execution via file uploads and plugin management. The same insecure-default pattern extends to database credentials (avideo/avideo), compounding the risk. Exploitation depends on operators failing to change the default, a condition likely met in quick-start, demo, and automated deployments. This issue has been fixed in version 26.0.