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

New CVE Detected

CVE-2026-86728 – Unauthenticated Sensitive Data Disclosure – WWBN AVideo ≤ 29.0

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

Summary

CVE-2026-86728 is a missing-authentication vulnerability (CWE-306) in AVideo, the open-source video/streaming platform maintained by WWBN. The flaw resides in the plugin/PlayLists/epg.json.php endpoint, which serializes live-stream credentials and EPG (electronic program guide) data without requiring any authentication. It is rated HIGH severity (CVSS v4.0 base score 8.7) and affects all AVideo versions through 29.0.

Technical details

  • Root cause: epg.json.php performs no authentication check and does not apply the PlayLists::showOnTV() filtering used by sibling endpoints (epg.xml.php, iptv.php) before serializing EPG objects.
  • Trigger conditions: An attacker sends unauthenticated HTTP requests to the endpoint, supplying sequential user or playlist IDs to enumerate targets.
  • Attack vector: Network-based, no privileges or user interaction required.
  • Impact: Disclosure of live-stream transmission keys (which function as administrative credentials), live server identifiers, M3U8/RTMP streaming links, and complete private programme schedules; sequential ID probing also enables user and playlist enumeration.

Affected software

  • WWBN AVideo, all versions through 29.0 (version 0 up to and including 29.0)

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No patched version is currently available from the vendor.
  • Workarounds/network mitigations:
    • Restrict or block external access to plugin/PlayLists/epg.json.php at the web server or reverse proxy/WAF layer until a fix is released.
    • Apply authentication requirements (e.g., User::isLogged() or equivalent) in front of the endpoint.
    • Implement the same showOnTV() filtering used by related endpoints, and strip sensitive fields (particularly stream key values) from responses served to unauthenticated users.
    • Require ownership verification before returning playlist/user-specific EPG data.
    • Monitor logs for sequential ID enumeration patterns against this endpoint.

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge