CVE-2026-33650: CWE-863: Incorrect Authorization in WWBN AVideo
CVE-2026-33650 is a high-severity authorization vulnerability in WWBN AVideo versions up to 26. 0. It allows users with the 'Videos Moderator' permission, which is intended only for changing video publicity status, to escalate privileges and perform full video management, including transferring ownership and deleting any video. The flaw arises from inconsistent authorization checks: full video editing requires 'canModerateVideos()' permission, but video deletion only verifies ownership, enabling a two-step exploit to transfer ownership then delete videos. No user interaction is required, and the vulnerability can be exploited remotely with low attack complexity. Although no known exploits are reported in the wild, affected organizations should apply the patch referenced in commit 838e16818c793779406ecbf34ebaeba9830e33f8 promptly. This vulnerability impacts confidentiality, integrity, and availability of video content on affected platforms.
AI Analysis
Technical Summary
WWBN AVideo is an open-source video platform used for hosting and managing video content. In versions up to and including 26.0, a critical authorization flaw (CWE-863) exists that allows privilege escalation by users assigned the 'Videos Moderator' role. This role is documented to permit only changes to video publicity status (Active, Inactive, Unlisted). However, due to inconsistent authorization logic, these users can escalate privileges to perform full video management operations, including transferring ownership and deleting any video. The root cause lies in the use of the 'Permissions::canModerateVideos()' function as an authorization gate in 'videoAddNew.json.php' for full video editing, while 'videoDelete.json.php' only checks if the user owns the video before allowing deletion. This asymmetry enables a two-step attack: first, the attacker transfers ownership of a target video to themselves, then deletes it, bypassing intended restrictions. The vulnerability has a CVSS 3.1 score of 7.6 (high severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and impacts on confidentiality, integrity, and availability. Although no known exploits are currently reported, the vulnerability poses a significant risk to the integrity and availability of video content on affected installations. A patch addressing this issue is available in commit 838e16818c793779406ecbf34ebaeba9830e33f8.
Potential Impact
This vulnerability allows attackers with limited privileges to escalate their permissions and fully control video content, including deleting or transferring ownership of any video on the platform. The impact includes unauthorized deletion or modification of video content, leading to loss of data integrity and availability. Confidentiality is also affected as unauthorized users may gain control over videos they should not manage. Organizations relying on WWBN AVideo for content delivery, especially those with multiple user roles, risk content sabotage, disruption of service, and potential reputational damage. Since the attack requires only low privileges and no user interaction, it can be exploited remotely by insiders or compromised accounts with 'Videos Moderator' permissions. This could disrupt business operations, cause data loss, and undermine trust in the platform’s security controls.
Mitigation Recommendations
Organizations should immediately update WWBN AVideo to a version that includes the patch from commit 838e16818c793779406ecbf34ebaeba9830e33f8 or later. Until patched, restrict the 'Videos Moderator' permission to trusted users only and audit current users assigned this role. Implement additional monitoring and alerting for unusual video ownership changes or deletions. Review and harden authorization logic in custom deployments to ensure consistent permission checks across all video management operations. Employ role-based access control (RBAC) best practices to minimize privilege assignments. Regularly audit logs for suspicious activity related to video management. Consider isolating critical video content or using external backup solutions to mitigate potential data loss from unauthorized deletions.
Affected Countries
United States, Germany, France, United Kingdom, Canada, Australia, India, Brazil, Japan, South Korea
CVE-2026-33650: CWE-863: Incorrect Authorization in WWBN AVideo
Description
CVE-2026-33650 is a high-severity authorization vulnerability in WWBN AVideo versions up to 26. 0. It allows users with the 'Videos Moderator' permission, which is intended only for changing video publicity status, to escalate privileges and perform full video management, including transferring ownership and deleting any video. The flaw arises from inconsistent authorization checks: full video editing requires 'canModerateVideos()' permission, but video deletion only verifies ownership, enabling a two-step exploit to transfer ownership then delete videos. No user interaction is required, and the vulnerability can be exploited remotely with low attack complexity. Although no known exploits are reported in the wild, affected organizations should apply the patch referenced in commit 838e16818c793779406ecbf34ebaeba9830e33f8 promptly. This vulnerability impacts confidentiality, integrity, and availability of video content on affected platforms.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
WWBN AVideo is an open-source video platform used for hosting and managing video content. In versions up to and including 26.0, a critical authorization flaw (CWE-863) exists that allows privilege escalation by users assigned the 'Videos Moderator' role. This role is documented to permit only changes to video publicity status (Active, Inactive, Unlisted). However, due to inconsistent authorization logic, these users can escalate privileges to perform full video management operations, including transferring ownership and deleting any video. The root cause lies in the use of the 'Permissions::canModerateVideos()' function as an authorization gate in 'videoAddNew.json.php' for full video editing, while 'videoDelete.json.php' only checks if the user owns the video before allowing deletion. This asymmetry enables a two-step attack: first, the attacker transfers ownership of a target video to themselves, then deletes it, bypassing intended restrictions. The vulnerability has a CVSS 3.1 score of 7.6 (high severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, and impacts on confidentiality, integrity, and availability. Although no known exploits are currently reported, the vulnerability poses a significant risk to the integrity and availability of video content on affected installations. A patch addressing this issue is available in commit 838e16818c793779406ecbf34ebaeba9830e33f8.
Potential Impact
This vulnerability allows attackers with limited privileges to escalate their permissions and fully control video content, including deleting or transferring ownership of any video on the platform. The impact includes unauthorized deletion or modification of video content, leading to loss of data integrity and availability. Confidentiality is also affected as unauthorized users may gain control over videos they should not manage. Organizations relying on WWBN AVideo for content delivery, especially those with multiple user roles, risk content sabotage, disruption of service, and potential reputational damage. Since the attack requires only low privileges and no user interaction, it can be exploited remotely by insiders or compromised accounts with 'Videos Moderator' permissions. This could disrupt business operations, cause data loss, and undermine trust in the platform’s security controls.
Mitigation Recommendations
Organizations should immediately update WWBN AVideo to a version that includes the patch from commit 838e16818c793779406ecbf34ebaeba9830e33f8 or later. Until patched, restrict the 'Videos Moderator' permission to trusted users only and audit current users assigned this role. Implement additional monitoring and alerting for unusual video ownership changes or deletions. Review and harden authorization logic in custom deployments to ensure consistent permission checks across all video management operations. Employ role-based access control (RBAC) best practices to minimize privilege assignments. Regularly audit logs for suspicious activity related to video management. Consider isolating critical video content or using external backup solutions to mitigate potential data loss from unauthorized deletions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T15:23:42.217Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c18a60f4197a8e3b8159f6
Added to database: 3/23/2026, 6:45:52 PM
Last enriched: 3/23/2026, 7:00:58 PM
Last updated: 3/23/2026, 8:38:25 PM
Views: 6
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.