WWBN AVideo has an incomplete fix for CVE-2026-33502: Command Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-41064: 0.34% estimated exploitation activity in the next 30 days; percentile 26.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The incomplete fix for AVideo's test.php adds escapeshellarg for wget but leaves the filegetcontents and curl code paths unsanitized, and the URL validation regex /^http/ accepts strings like httpevil.com. Affected Package - Ecosystem: Other - Package: AVideo - Affected versions: < commit 1e6cf03e93b5 - Patched versions: = commit 1e6cf03e93b5 Details The vulnerable wget() function in plugin/Live/test.php: Neither $url nor $filename is passed through escapeshellarg(). The URL validation uses pregmatch("/^http/", $url) which: - Does not require :// (matches httpevil.com) - Does not block shell metacharacters (;, backticks, $()) - Does not validate the URL is actually a URL A payload like http://x; id /tmp/pwned; echo passes the regex and injects arbitrary commands via the semicolons. The fix adds escapeshellarg() for the wget path and an isAllowedStatsTestURL allowlist, but urlgetcontents() (used by the same endpoint) still follows redirects without validation. The…

Published by the source

14 Apr 2026, 23:27 UTC

Last modified by the source

24 Apr 2026, 20:41 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pq8p-wc4f-vg7j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41064

Advisory: WWBN AVideo has an incomplete fix for CVE-2026-33502: Command Injection
IDs: CVE-2026-41064, GHSA-pq8p-wc4f-vg7j
Record: https://patchnext.com/advisories/cve-2026-41064 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected <= 29.0

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pq8p-wc4f-vg7j (GitHub-reviewed advisory GHSA-pq8p-wc4f-vg7j lists affected ranges: Packagist wwbn/avideo >=0 <=29.0)

Commands are suggestions: review each one before running it.