CVE-2026-33037: CWE-1188: Insecure Default Initialization of Resource in WWBN AVideo
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.
AI Analysis
Technical Summary
CVE-2026-33037 is a vulnerability in WWBN AVideo, an open-source video platform, affecting versions 25.0 and earlier. The root cause is insecure default initialization of critical credentials in the official Docker deployment files (docker-compose.yml and env.example). Specifically, the admin password is hardcoded as 'password' and automatically assigned to the admin account during installation if the SYSTEM_ADMIN_PASSWORD environment variable is not overridden. There are no compensating controls such as forced password changes on first login, password complexity enforcement, or detection of default passwords. Additionally, the password is hashed using the weak MD5 algorithm, which is vulnerable to collision and preimage attacks. The database credentials also use insecure default values (username: avideo, password: avideo), further increasing the attack surface. Exploitation requires no authentication or user interaction and can lead to full administrative access, allowing attackers to expose user data, manipulate video content, and execute remote code through file uploads and plugin management features. This vulnerability is particularly dangerous in quick-start, demo, or automated deployments where operators may neglect to change default credentials. The vulnerability has been assigned a CVSS 3.1 score of 8.1 (high severity) and was fixed in version 26.0 of AVideo.
Potential Impact
The impact of CVE-2026-33037 is significant for organizations deploying WWBN AVideo versions 25.0 and below, especially those using the official Docker deployment method without overriding default credentials. Successful exploitation results in complete administrative takeover, compromising confidentiality, integrity, and availability of the platform. Attackers can access sensitive user data, alter or delete video content, and potentially execute arbitrary code on the hosting server, leading to full system compromise. This can result in data breaches, service disruption, reputational damage, and potential lateral movement within the victim's network. The ease of exploitation (no authentication or user interaction required) and the widespread use of Docker for deployment increase the likelihood of successful attacks, particularly in environments where rapid deployment or demos are common. The insecure default database credentials further exacerbate the risk by enabling attackers to access backend data stores directly.
Mitigation Recommendations
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.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Japan, South Korea, India, Brazil
CVE-2026-33037: CWE-1188: Insecure Default Initialization of Resource in WWBN AVideo
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33037 is a vulnerability in WWBN AVideo, an open-source video platform, affecting versions 25.0 and earlier. The root cause is insecure default initialization of critical credentials in the official Docker deployment files (docker-compose.yml and env.example). Specifically, the admin password is hardcoded as 'password' and automatically assigned to the admin account during installation if the SYSTEM_ADMIN_PASSWORD environment variable is not overridden. There are no compensating controls such as forced password changes on first login, password complexity enforcement, or detection of default passwords. Additionally, the password is hashed using the weak MD5 algorithm, which is vulnerable to collision and preimage attacks. The database credentials also use insecure default values (username: avideo, password: avideo), further increasing the attack surface. Exploitation requires no authentication or user interaction and can lead to full administrative access, allowing attackers to expose user data, manipulate video content, and execute remote code through file uploads and plugin management features. This vulnerability is particularly dangerous in quick-start, demo, or automated deployments where operators may neglect to change default credentials. The vulnerability has been assigned a CVSS 3.1 score of 8.1 (high severity) and was fixed in version 26.0 of AVideo.
Potential Impact
The impact of CVE-2026-33037 is significant for organizations deploying WWBN AVideo versions 25.0 and below, especially those using the official Docker deployment method without overriding default credentials. Successful exploitation results in complete administrative takeover, compromising confidentiality, integrity, and availability of the platform. Attackers can access sensitive user data, alter or delete video content, and potentially execute arbitrary code on the hosting server, leading to full system compromise. This can result in data breaches, service disruption, reputational damage, and potential lateral movement within the victim's network. The ease of exploitation (no authentication or user interaction required) and the widespread use of Docker for deployment increase the likelihood of successful attacks, particularly in environments where rapid deployment or demos are common. The insecure default database credentials further exacerbate the risk by enabling attackers to access backend data stores directly.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T18:10:50.210Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bdbd96e2bf98efc48d1059
Added to database: 3/20/2026, 9:35:18 PM
Last enriched: 3/27/2026, 10:51:06 PM
Last updated: 5/1/2026, 3:51:44 AM
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.