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

New CVE Detected

CVE-2026-63305 – Unauthenticated OS Command Injection (RCE) – WWBN AVideo through 29.0

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

Summary

CVE-2026-63305 is a critical OS command injection vulnerability (CWE-78) in WWBN AVideo affecting all versions through 29.0. The flaw resides in the ffmpeg.json.php endpoint, where the notifyCode and callback parameters are concatenated directly into a shell command without sanitization, enabling unauthenticated remote attackers who can craft a valid encrypted payload to execute arbitrary OS commands as the web-server user. The vulnerability carries a CVSS v4.0 score of 9.2 (Critical) and a CVSS v3.1 score of 8.1 (High).

Technical details

  • Root cause: Within plugin/API/standAlone/ffmpeg.json.php, the notifyCode and callback parameters sourced from the decrypted codeToExec object are concatenated raw into a shell command executed via nohup sh -c. Unlike the adjacent notify parameter — which is properly protected with escapeshellarg() — these two fields receive no equivalent sanitization and bypass the sanitizeFFmpegCommand() denylist, leaving them directly injectable.
  • Trigger conditions: An attacker must craft a validly encrypted codeToExec payload with a timestamp within 30 seconds of the server’s current time. No user account or interactive authentication is required (Privileges Required: NONE).
  • Attack vector: Remote, unauthenticated, over the network via HTTP/HTTPS.
  • Impact: Injection of shell metacharacters (;, $(...), backticks) into notifyCode or callback results in arbitrary OS command execution as the web-server user — a full remote code execution primitive with high impact to confidentiality, integrity, and availability.

Affected software

  • WWBN AVideo all versions through 29.0

Severity

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

  • No vendor patch has been released as of the publication of this advisory. Monitor the WWBN AVideo GitHub repository and the associated security advisory (GHSA-g9x9-q7qj-6mv5) for remediation releases.
  • Network mitigation (immediate): Block or restrict external access to the ffmpeg.json.php endpoint at the web application firewall or network perimeter. Internet-facing AVideo instances should be treated as high-risk until a patch is available.
  • Consider taking exposed instances offline or placing them behind strict network access controls until the vendor releases a fix.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate mitigation. 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