dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-63304

HIGH · 8.1 CVSS v3.1 Published 2026-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
AVideo through 29.0 contains an OS command injection vulnerability in plugin/API/standAlone/functions.php where the listFFmpegProcesses() function interpolates unsanitized keyword parameters inside single quotes without escaping. Attackers who can craft a valid encrypted codeToExec payload can break out of the single-quoted grep context and execute arbitrary OS commands as the web-server user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

AVideo through 29.0 has an OS command injection vulnerability in the listFFmpegProcesses() function within plugin/API/standAlone/functions.php. The function takes a keyword parameter that gets interpolated directly into a grep command inside single quotes without proper sanitization, allowing attackers with a valid encrypted codeToExec payload to break out of the quotes and execute arbitrary OS commands as the web server user.

MitigationSanitize and properly escape all user-supplied keyword parameters before using them in shell commands, or refactor to use parameterized approaches that avoid shell invocation entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AVideo installation and locate the web root
    Search for the AVideo installation directory. Look for index.php or the main AVideo files. Common locations include /var/www/html/, /var/www/, or custom web directories.
    Affected if AVideo is not found on the system - you are not affected.
  2. Check AVideo version against the affected range
    Locate the version file or check the main index.php for a version identifier. Compare it to the affected range (version 29.0 and below).
    Affected if Your installed version is 29.0 or lower - proceed to next checks. If version is unknown or higher than 29.0, you are likely not affected by this specific CVE.
  3. Verify the vulnerable file exists
    Check for the presence of plugin/API/standAlone/functions.php within your AVideo installation directory.
    Affected if The file does not exist - you are likely not affected. The file exists - proceed to next checks.
  4. Inspect the listFFmpegProcesses function
    Open plugin/API/standAlone/functions.php and locate the listFFmpegProcesses function. Look for how the keyword parameter is used in system commands, specifically within single-quoted grep contexts.
    Affected if The function exists and uses the keyword parameter in unsanitized system calls - you are potentially affected. The function is properly escaped or does not exist - you are likely not affected.
  5. Determine if the API endpoint is accessible
    The vulnerability requires a valid encrypted codeToExec payload sent to the API endpoint. Check if the API functionality is exposed and whether external attackers could reach this endpoint.
    Affected if The API endpoint is publicly accessible without strict access controls - you are at higher risk. The endpoint is internal-only or properly protected - your exposure is reduced.

You are affected if AVideo version 29.0 or lower is installed, the vulnerable listFFmpegProcesses function exists in the expected location with unsanitized keyword parameter handling, and the API endpoint is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Sanitize and properly escape all user-supplied keyword parameters before using them in shell commands, or refactor to use parameterized approaches that avoid shell invocation entirely.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-63304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-63304 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data