p PatchFirst

PatchFirst · Latest vulnerabilities

wwbn/avideo 21.0: known vulnerabilities · Page 8

Known vulnerabilities affecting wwbn/avideo 21.0: 146. Compare the fixes below with your installed release.

Filter vulnerabilities
Clear filters

Vulnerabilities: 146

  1. CVE-2026-33035

    Medium · CVSS 5.3EPSS 0.32%No fix published

    Unauthenticated Reflected XSS via innerHTML in AVideo

    WWBN AVideo is an open source video platform. In versions 25.0 and below, there is a reflected XSS vulnerability that allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser. User input from a URL parameter flows through PHP's json_encode() into a JavaScript function that renders it via innerHTML, bypassing encoding and achieving full script execution. The vulnerability is caused by two issues working together: unescaped user input passed to JavaScript (videoNotFound.php), and innerHTML rendering HTML tags as executable DOM (script.js). The attack can be escalated to steal session cookies, take over accounts, p

    Published Updated
  2. CVE-2026-30885

    Medium · CVSS 5.5EPSS 0.39%Fix available

    WWBN AVideo - Unauthenticated IDOR - Playlist Information Disclosure

    WWBN AVideo is an open source video platform. Prior to 25.0, the /objects/playlistsFromUser.json.php endpoint returns all playlists for any user without requiring authentication or authorization. An unauthenticated attacker can enumerate user IDs and retrieve playlist information including playlist names, video IDs, and playlist status for any user on the platform. This vulnerability is fixed in 25.0.

    • Update to 25.0
    Published Updated
  3. CVE-2026-28501

    Critical · CVSS 9.8EPSS 1.57%Public exploitNo fix published

    WWBN AVideo: Unauthenticated SQL Injection via JSON Request Bypass in objects/videos.json.php

    WWBN AVideo is an open source video platform. Prior to version 24.0, an unauthenticated SQL Injection vulnerability exists in AVideo within the objects/videos.json.php and objects/video.php components. The application fails to properly sanitize the catName parameter when it is supplied via a JSON-formatted POST request body. Because JSON input is parsed and merged into $_REQUEST after global security checks are executed, the payload bypasses the existing sanitization mechanisms. This issue has been patched in version 24.0.

    Published Updated
  4. CVE-2026-28502

    Critical · CVSS 9.3EPSS 0.7%No fix published

    WWBN AVideo: Authenticated Remote Code Execution via Unsafe Plugin ZIP Extraction

    WWBN AVideo is an open source video platform. Prior to version 24.0, an authenticated Remote Code Execution (RCE) vulnerability was identified in AVideo related to the plugin upload/import functionality. The issue allowed an authenticated administrator to upload a specially crafted ZIP archive containing executable server-side files. Due to insufficient validation of extracted file contents, the archive was extracted directly into a web-accessible plugin directory, allowing arbitrary PHP code execution. This issue has been patched in version 24.0.

    Published Updated
  5. CVE-2026-29093

    High · CVSS 8.1EPSS 0.51%No fix published

    WWBN AVideo: Unauthenticated PHP session store exposed to host network via published memcached port

    WWBN AVideo is an open source video platform. Prior to version 24.0, the official docker-compose.yml publishes the memcached service on host port 11211 (0.0.0.0:11211) with no authentication, while the Dockerfile configures PHP to store all user sessions in that memcached instance. An attacker who can reach port 11211 can read, modify, or flush session data — enabling session hijacking, admin impersonation, and mass session destruction without any application-level authentication. This issue has been patched in version 24.0.

    Published Updated
  6. CVE-2026-27732

    High · CVSS 8.6EPSS 0.27%Fix available

    AVideo has Authenticated Server-Side Request Forgery via downloadURL in aVideoEncoder.json.php

    WWBN AVideo is an open source video platform. Prior to version 22.0, the `aVideoEncoder.json.php` API endpoint accepts a `downloadURL` parameter and fetches the referenced resource server-side without proper validation or an allow-list. This allows authenticated users to trigger server-side requests to arbitrary URLs (including internal network endpoints). An authenticated attacker can leverage SSRF to interact with internal services and retrieve sensitive data (e.g., internal APIs, metadata services), potentially leading to further compromise depending on the deployment environment. This issue has been fixed in AVideo version 22.0.

    • Update to 22.0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →