Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-84187 – Unauthenticated Denial of Service via RTMP Callback – WWBN AVideo ≤ 29.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-84187 is a missing-authentication vulnerability (CWE-284) in the AVideo platform’s RTMP callback handler, plugin/Live/on_publish.php. Unauthenticated attackers can send crafted POST requests to this endpoint to mark arbitrary scheduled live broadcasts as failed, silently disrupting streaming operations. The issue affects AVideo version 29.0 and earlier and carries a High severity rating.

Technical details

  • Root cause: on_publish.php is missing the Live::assertRtmpCallbackAllowed() check that is present in sibling RTMP callback files (on_publish_done.php, on_record_done.php), so the endpoint never verifies that the request actually originates from the trusted RTMP server.
  • Trigger conditions: An attacker sends a POST request with a name parameter containing a fabricated stream key matching the pattern -ps-<N>, where N is a schedule identifier. The code extracts the schedule ID without verifying the key belongs to that schedule or that the caller is authorized.
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity.
  • Impact: The request reaches on_publish_denied(), which updates the corresponding scheduled broadcast’s status to "failed," allowing any internet-facing attacker to cancel or disrupt arbitrary scheduled live broadcasts by iterating schedule IDs. All requests return identical responses, leaving no distinguishing attack signature.

Affected software

  • WWBN AVideo: all versions up to and including 29.0

Severity

CVSS v3.1 Base Score: 8.2 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

(Note: AVideo’s own advisory and CVE record also list a CVSS v3.1/High rating in the 8.2–8.8 range depending on scoring standard used.)

Mitigation and recommended actions

  • Immediate: No patched AVideo release has been published at the time of advisory disclosure. Monitor the vendor’s GitHub security advisory (GHSA-v395-2xmq-cg23) for a fix that adds the missing Live::assertRtmpCallbackAllowed() check to on_publish.php, and upgrade as soon as it is released.
  • If no patch is available:
    • Restrict network access to the RTMP callback endpoints (plugin/Live/on_publish.php and related files) so they are reachable only from the trusted RTMP/media server, not the public internet.
    • Deploy a web application firewall (WAF) rule to block external POST requests to on_publish.php that are not sourced from the internal streaming server’s IP.
    • Monitor scheduled broadcast status changes for unexpected transitions to "failed" as a sign of exploitation attempts.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Sign In - AVideo, AVideo
  • Raw response body: id="avideoModal", avideoAlert(, avideoModalIframe(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge