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

New CVE Detected

CVE-2026-63304 – OS Command Injection / RCE – AVideo (WWBN) through version 29.0

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

Summary

CVE-2026-63304 is a critical OS command injection vulnerability (CWE-78) affecting WWBN AVideo, an open-source, self-hosted video streaming and broadcasting platform, in all versions through 29.0. An attacker who can supply a valid encrypted codeToExec payload can break out of a single-quoted shell context inside the listFFmpegProcesses() function and execute arbitrary OS commands as the web-server user. No patch is currently available in a released version of AVideo.

Technical details

  • Root cause: The listFFmpegProcesses() function in plugin/API/standAlone/functions.php constructs a shell command by appending a user-controlled keyword value directly inside single quotes without any escaping: $command .= " | grep '$keyword'";. Two API modes — list and isKeywordRunning — pass decrypted input to this function without further sanitization, bypassing allowlisting applied elsewhere in the codebase.
  • Trigger condition: An attacker must supply a valid AES-256-CBC-encrypted payload (using the application’s APISecret key) for the codeToExec parameter. Once a valid encrypted payload is crafted, the injected keyword value is passed unescaped to the shell, allowing breakout with payloads such as x'; <command> #.
  • Attack vector: Network-accessible, unauthenticated HTTP/HTTPS request to the standalone API endpoint. No privileges and no user interaction are required.
  • Impact: Arbitrary OS command execution as the web-server user, enabling file system access, credential theft (e.g., database credentials), data exfiltration, and persistent access to the host.

Affected software

  • WWBN AVideo — all versions through 29.0 (latest released version at time of publication)

Severity

  • CVSS v4.0 Base Score: 9.2 (Critical)
    Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 8.1 (High)
    Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Patch: No fixed release is available at the time of publication. Monitor the WWBN AVideo GitHub repository for a patched version and upgrade immediately upon release.
  • Workaround — restrict endpoint access: Block or restrict external access to the /plugin/API/standAlone/ path at the network perimeter (WAF, reverse proxy, or firewall rules) to reduce exposure until a patch is available.
  • Workaround — protect the APISecret: Ensure the application’s APISecret key is not exposed through other vulnerabilities (e.g., information disclosure, database dump). Related AVideo CVEs disclosed in 2026 (such as CVE-2026-33478) demonstrate that key material can be retrieved via chained attacks; remediating those issues reduces the likelihood of codeToExec payload forgery.
  • Suggested code fix (per advisory): Wrap the keyword parameter with escapeshellarg() at the shell boundary inside listFFmpegProcesses() to prevent single-quote breakout.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

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