AVideo Vulnerable to OS Command Injection via Unsanitized users_id and liveTransmitionHistory_id in Restreamer Log File Path

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33648: 0.64% estimated exploitation activity in the next 30 days; percentile 50.52 (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 restreamer endpoint constructs a log file path by embedding user-controlled usersid and liveTransmitionHistoryid values from the JSON request body without any sanitization. This log file path is then concatenated directly into shell commands passed to exec(), allowing an authenticated user to achieve arbitrary command execution on the server via shell metacharacters such as $() or backticks. Details The vulnerability exists in plugin/Live/standAloneFiles/restreamer.json.php. The data flow is: 1. User input ingestion (line 220): 2. Log file template (line 58): 3. usersid injected without sanitization (line 318): 4. liveTransmitionHistoryid injected without sanitization (line 407): Note: intval() is applied to liveTransmitionHistoryid in the separate getProcess() function (line 805), but NOT in the runRestream() path that constructs the log file. 5. Unsanitized log file path passed to exec() (lines 720, 723): The code sanitizes stream URLs via clearCommandURL() and uses…

Published by the source

25 Mar 2026, 17:47 UTC

Last modified by the source

25 Mar 2026, 17:47 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5m4q-5cvx-36mw

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

# Patch Next advisory brief: CVE-2026-33648

Advisory: AVideo Vulnerable to OS Command Injection via Unsanitized `users_id` and `liveTransmitionHistory_id` in Restreamer Log File Path
IDs: CVE-2026-33648, GHSA-5m4q-5cvx-36mw
Record: https://patchnext.com/advisories/cve-2026-33648 (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 <= 26.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-5m4q-5cvx-36mw (GitHub-reviewed advisory GHSA-5m4q-5cvx-36mw lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.