dbcve.org
AvideoApplication · Wwbn

CVE-2026-45578

HIGH · 8.8 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to after 29.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
WWBN AVideo is an open source video platform. In 29.0 and earlier, there is a classic shell-metacharacter injection. The YPTSocket notification branch in plugin/Live/on_publish.php builds an execAsync() command line by string concatenation, single-quoting each argument but never calling escapeshellarg(). A ' in any of the three interpolated values ($users_id, $m3u8, $obj->liveTransmitionHistory_id) closes the quoted token and lets the attacker append arbitrary commands.

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 · high confidence

Command injection vulnerability in plugin/Live/on_publish.php where execAsync() constructs shell commands using string concatenation with single quotes around $users_id, $m3u8, and $obj->liveTransmitionHistory_id without calling escapeshellarg(), allowing attackers to inject arbitrary commands via a single quote that breaks out of the quoted context.

MitigationApply escapeshellarg() to all three user-controlled variables ($users_id, $m3u8, $obj->liveTransmitionHistory_id) before interpolating them into the execAsync() command string, or refactor to use an array-based approach that avoids shell invocation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvideoApplication
Affected:<= 29.0

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Check the version.php file in the AVideo root directory, or look for a version identifier in the admin panel under 'About' or 'System Configuration'. Compare the installed version to the affected range (<=29.0).
    Affected if The installed version is 29.0 or lower.
  2. Locate the vulnerable file
    Verify that the file plugin/Live/on_publish.php exists in the AVideo installation directory.
    Affected if The file plugin/Live/on_publish.php is present.
  3. Verify the Live plugin is enabled
    Check the plugin configuration in the AVideo admin panel to confirm the Live plugin is active, or inspect the database table 'plugins' for a record where 'name' contains 'Live' and 'enabled' is set to 1.
    Affected if The Live plugin is enabled in the system.
  4. Inspect vulnerable code pattern
    Examine plugin/Live/on_publish.php and search for the execAsync() function calls. Look for string concatenation using single quotes around variables ($users_id, $m3u8, $obj->liveTransmitionHistory_id) WITHOUT preceding escapeshellarg() calls.
    Affected if Code shows execAsync() calls with single-quoted string concatenation around user-controlled variables without escapeshellarg() applied to those variables.
  5. Check for exploitation indicators
    Review web server access logs (Apache/Nginx) for requests to plugin/Live/on_publish.php containing suspicious patterns such as single quotes, semicolons, pipe symbols (|), backticks ($), or command substitution syntax in the parameters.
    Affected if Logs show anomalous shell metacharacters in requests to the vulnerable endpoint.

You are affected if you are running Avideo version 29.0 or lower, the Live plugin is enabled, and the vulnerable code pattern (execAsync with unescaped variables) exists in plugin/Live/on_publish.php.

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
Upgrade available Upgrade to a release after 29.0
Interim mitigation

Apply escapeshellarg() to all three user-controlled variables ($users_id, $m3u8, $obj->liveTransmitionHistory_id) before interpolating them into the execAsync() command string, or refactor to use an array-based approach that avoids shell invocation.

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45578 — 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-45578 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