CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-33650

CVE-2026-33650: Privilege Escalation via Incorrect Authorization in WWBN AVideo

Alon Barad
Alon Barad
Software Engineer

Mar 25, 2026·5 min read·51 visits

Executive Summary (TL;DR)

A privilege escalation flaw in WWBN AVideo <= 26.0 allows 'Videos Moderator' users to bypass authorization checks, transfer arbitrary video ownership to themselves, and subsequently delete videos they do not own.

WWBN AVideo versions up to and including 26.0 contain an incorrect authorization vulnerability (CWE-863). Users with the 'Videos Moderator' permission can exploit inconsistent authorization boundaries to transfer video ownership and delete arbitrary videos, resulting in privilege escalation.

Vulnerability Overview

WWBN AVideo is an open-source video hosting platform utilized for internal and public video distribution. In versions 26.0 and earlier, the application suffers from an incorrect authorization vulnerability mapped to CWE-863. This flaw resides within the video management endpoints, specifically the API responsible for updating video metadata.

The vulnerability allows users provisioned with the "Videos Moderator" role to escalate their privileges. Although this role is strictly intended to toggle video visibility states such as Active, Inactive, or Unlisted, the backend API grants these users broader permissions. This architectural oversight exposes sensitive video management operations to unauthorized modification.

An attacker leveraging this vulnerability can permanently alter the ownership of any video hosted on the platform. By transferring ownership to their own account, the attacker bypasses subsequent ownership verification checks. This logical chain allows the attacker to unilaterally delete content belonging to other users, including system administrators.

Technical Root Cause Analysis

The core issue originates from an asymmetric authorization boundary within the videoAddNew.json.php script. This endpoint processes updates to video metadata but implements an excessively permissive authorization gate. The application uses the Permissions::canModerateVideos() function to bypass the more restrictive Video::canEdit() verification logic.

When a request reaches videoAddNew.json.php, the code evaluates whether the requesting user is the video owner or a moderator. The inclusion of the moderator permission check creates a logical vulnerability. It effectively grants moderators the same administrative capabilities over a video object as the original owner.

Deeper within the same script, the application processes ownership transfer instructions. The application logic specifically permits a user to update the users_id attribute of the video object if the Permissions::canModerateVideos() check returns true. Consequently, a moderator can submit a modified users_id parameter to reassign the target video to their own account.

The deletion endpoint, videoDelete.json.php, relies entirely on the Video::canEdit() function to validate authorization. Because the attacker successfully modified the video's underlying users_id attribute in the previous step, the deletion script evaluates the attacker as the legitimate owner. The deletion proceeds without triggering any access control violations.

Code Analysis and Patch Review

An examination of the vulnerable codebase reveals the exact nature of the authorization failure. In the unpatched objects/videoAddNew.json.php file, the initial gate check validates the request using a composite logical condition. The code executes if (!Video::canEdit($_POST['id']) && !Permissions::canModerateVideos()), which actively exempts moderators from standard editing constraints.

Further down the execution path, the script handles the metadata payload, including the owner ID assignment. The vulnerable implementation reads if ($advancedCustomUser->userCanChangeVideoOwner || Permissions::canModerateVideos()), followed directly by $obj->setUsers_id($_POST['users_id']). This explicit reliance on the moderator permission object facilitates the unauthorized ownership transfer.

The remediation, introduced in commit 838e16818c793779406ecbf34ebaeba9830e33f8, resolves this discrepancy by strictly enforcing appropriate permission models. The initial gate in videoAddNew.json.php was simplified to if (!Video::canEdit($_POST['id'])), entirely removing the moderator bypass.

Additionally, the patch modifies the authorization checks governing specific metadata fields. The codebase now requires the Permissions::canAdminVideos() validation before permitting modifications to categories, user groups, and ownership. This change ensures that only users with explicit administrative privileges can reassign video ownership.

Exploitation Methodology

Exploitation requires the attacker to possess an active account configured with the PERMISSION_INACTIVATEVIDEOS permission. The attacker must first identify the unique id parameter of the target video they intend to hijack. This ID is typically exposed in the platform's public-facing URLs or standard API responses.

The attack sequence begins with a crafted HTTP POST request directed at the /objects/videoAddNew.json.php endpoint. The attacker includes the target video's id and their own user ID in the users_id parameter. This request manipulates the application state, successfully severing the original owner's control over the video object.

To demonstrate the full impact, the attacker proceeds to the deletion phase. The attacker issues a second HTTP POST request to the /objects/videoDelete.json.php endpoint, supplying only the hijacked video's id. The application evaluates the attacker's newly established ownership and permanently removes the video from the platform.

The exploitation flow requires no advanced tooling and can be executed using standard web proxies or command-line HTTP clients. The attack leaves minimal traces beyond standard application access logs, complicating post-incident analysis.

Impact Assessment

The successful exploitation of CVE-2026-33650 severely degrades the integrity and availability of the hosted video platform. An authenticated attacker with low-level moderator privileges gains the capacity to systematically dismantle the application's content library. The attacker exercises unilateral control over all video assets, regardless of the original publisher's administrative tier.

The CVSS v3.1 base score of 7.6 reflects the severity of this privilege escalation. The attack operates entirely over the network without requiring any interaction from the victim. The integrity metric is rated High due to the complete compromise of ownership metadata, while availability is rated Low to reflect the specific loss of individual video objects rather than full system downtime.

Organizations relying on AVideo for internal training, corporate communications, or monetized content distribution face significant operational disruption. The unauthorized removal of critical video assets directly impacts business continuity. Furthermore, the ability to modify metadata allows the attacker to alter video categories or titles, facilitating content defacement.

Official Patches

WWBNOfficial Fix Commit
WWBNGitHub Security Advisory

Fix Analysis (1)

Technical Appendix

CVSS Score
7.6/ 10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
EPSS Probability
0.03%
Top 100% most exploited

Affected Systems

WWBN AVideo <= 26.0

Affected Versions Detail

Product
Affected Versions
Fixed Version
AVideo
WWBN
<= 26.0Commit 838e16818c793779406ecbf34ebaeba9830e33f8
AttributeDetail
CWE IDCWE-863
Attack VectorNetwork
CVSS Score7.6
EPSS Score0.00028
ImpactHigh Integrity, Low Availability
Exploit StatusProof of Concept
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1068Exploitation for Privilege Escalation
Privilege Escalation
CWE-863
Incorrect Authorization

The software does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Known Exploits & Detection

GitHub Security AdvisoryExploitation methodology documented in the vendor advisory.

Vulnerability Timeline

Patch committed to the official repository.
2026-03-22
Public disclosure and GHSA/CVE assignment.
2026-03-23
NVD publication and CVSS scoring completed.
2026-03-25

References & Sources

  • [1]Official Fix Commit
  • [2]GitHub Security Advisory
  • [3]CVE Record
  • [4]NVD Entry

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•44 minutes ago•CVE-2026-114156
6.5

CVE-2026-114156: Path Equivalence Security Feature Bypass in Microsoft ASP.NET Core

CVE-2026-114156 is an improper resolution of path equivalence vulnerability (CWE-41) in Microsoft ASP.NET Core affecting .NET 11.0 preview releases and Microsoft Visual Studio 2026. The vulnerability stems from a discrepancy between how path prefix validation helpers (such as PathString.StartsWithSegments) and downstream routing mechanisms handle alternate path separators and percent-encoded characters. An unauthenticated remote attacker can exploit this mismatch over the network to bypass path-based authorization middleware and access restricted endpoints.

Amit Schendel
Amit Schendel
1 views•8 min read
•about 2 hours ago•CVE-2026-114157
7.5

CVE-2026-114157: Local Privilege Escalation via Race Condition in ASP.NET Core Kestrel Named Pipes Transport

CVE-2026-114157 is a high-severity local privilege escalation and security feature bypass vulnerability affecting ASP.NET Core on Microsoft Windows. The flaw resides in the Kestrel web server's Named Pipes transport layer (Microsoft.AspNetCore.Server.Kestrel.Transport.NamedPipes) and stems from a race condition (CWE-362) during broken pipe error recovery. When an active connection throws an IOException during handshake acceptance, the connection listener previously disposed of the broken NamedPipeServerStream instance before acquiring a replacement stream from its internal pool. This sequence created a momentary window where zero server instances of the named pipe existed in the Windows Named Pipe File System (NPFS). A local, low-privileged attacker can exploit this timing window to create a named pipe with the identical name and a permissive Discretionary Access Control List (DACL), hijacking subsequent inter-process communications and escalating privileges across security boundaries.

Amit Schendel
Amit Schendel
4 views•11 min read
•about 3 hours ago•CVE-2026-124194
6.5

CVE-2026-124194: Forced Authentication and NetNTLMv2 Credential Leakage in Microsoft Office Outlook

CVE-2026-124194 is a forced authentication and spoofing vulnerability in Microsoft Office Outlook caused by a missing user interface warning before dereferencing remote network paths (CWE-356). By embedding an attacker-controlled Universal Naming Convention (UNC) path within MAPI message properties such as PidLidReminderFileParameter, an unauthenticated remote attacker can force a victim's system to initiate an outbound SMB or WebDAV connection upon opening or previewing a crafted message. This automatic authentication handshake leaks the user's NetNTLMv2 hash, enabling offline password cracking or real-time NTLM relay attacks. The vulnerability was exploited in the wild as a zero-day prior to its remediation in Microsoft's November 2026 Patch Tuesday updates and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Alon Barad
Alon Barad
10 views•10 min read
•about 3 hours ago•CVE-2026-114154
7.5

CVE-2026-114154: Denial of Service in ASP.NET Core HttpSys Request Header Processing

CVE-2026-114154 is a high-severity Denial of Service (DoS) and uncontrolled resource consumption vulnerability in the Microsoft.AspNetCore.Server.HttpSys component of ASP.NET Core. When processing an HTTP request that simultaneously contains a chunked Transfer-Encoding header, a Content-Length header, and an explicit X-Content-Length header, the server throws an unhandled ArgumentException during header normalization. In certain versions, subsequent exception handling attempts to dereference a disposed native request context, aborting error response dispatch and leaking unmanaged HTTP.sys request structures.

Amit Schendel
Amit Schendel
4 views•9 min read
•about 4 hours ago•CVE-2026-120778
7.3

CVE-2026-120778: Local Elevation of Privilege via Insecure Temporary Directory Handling and MSBuild Response File Hijacking in Microsoft .NET Aspire CLI

A local elevation of privilege vulnerability exists in the Microsoft .NET Aspire CLI (`Aspire.Cli`) versions 13.5.4 prior to 13.6.5. When executing SDK management commands (`aspire sdk generate`, `aspire sdk dump`, and `aspire sdk export`), the CLI creates temporary project directories inside the shared operating system temporary folder (such as `/tmp` on Unix-like systems) without restricting directory permissions or disabling MSBuild automatic response file resolution. A local, low-privileged attacker on a multi-user system can place a crafted `Directory.Build.rsp` file in the shared temporary directory hierarchy. When a victim user executes an affected Aspire CLI command, MSBuild traverses upward, ingests the attacker-controlled response file, and executes arbitrary commands in the security context of the victim user.

Alon Barad
Alon Barad
4 views•10 min read
•about 5 hours ago•CVE-2026-120792
7.3

CVE-2026-120792: Local Information Disclosure via Temporary File Logging in Microsoft .NET Aspire CLI

CVE-2026-120792 is a high-severity local information disclosure vulnerability in the Microsoft .NET Aspire CLI (Aspire.Cli) affecting versions 13.5.4 prior to 13.6.5. The flaw stems from the insertion of sensitive information into a shared temporary log file (CWE-532) combined with insecure temporary file creation (CWE-377) within the DeprecatedMcpCommandScanner component. During agent configuration scanning, the CLI unconditionally appends internal workspace paths and the first 200 characters of Model Context Protocol (MCP) agent configuration files to a statically named file in the system temporary directory. On multi-user systems, unprivileged local users can read this file to harvest API keys, authentication tokens, and internal service endpoints.

Alon Barad
Alon Barad
4 views•9 min read