WWBN AVideo has Stored XSS via Unanchored Duration Regex in Video Encoder Receiver

Exploitation

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

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-41061: 0.17% estimated exploitation activity in the next 30 days; percentile 6.75 (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 isValidDuration() regex at objects/video.php:918 uses /^[0-9]{1,2}:[0-9]{1,2}:[0-9]{1,2}/ without a $ end anchor, allowing arbitrary HTML/JavaScript to be appended after a valid duration prefix. The crafted duration is stored in the database and rendered without HTML escaping via echo Video::getCleanDuration() on trending pages, playlist pages, and video gallery thumbnails, resulting in stored cross-site scripting. Details Input entry point: objects/aVideoEncoderReceiveImage.json.php:208 Insufficient validation: objects/video.php:918 The regex matches 00:00:01 at the start of the string but ignores everything after it. A payload like 00:00:01</time<img src=x onerror=alert(1)<time passes validation. No sanitization in output function: objects/video.php:3463-3480 With the payload 00:00:01</time<img src=x onerror=alert(1)<time, exploding by : yields 3+ parts, so the full unsanitized string is returned. Unescaped output sinks: 1. view/trending.php:72: 2.…

Published by the source

14 Apr 2026, 23:22 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-8pv3-29pp-pf8f

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

# Patch Next advisory brief: CVE-2026-41061

Advisory: WWBN AVideo has Stored XSS via Unanchored Duration Regex in Video Encoder Receiver
IDs: CVE-2026-41061, GHSA-8pv3-29pp-pf8f
Record: https://patchnext.com/advisories/cve-2026-41061 (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: Medium (CVSS 5.4)
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-8pv3-29pp-pf8f (GitHub-reviewed advisory GHSA-8pv3-29pp-pf8f lists affected ranges: Packagist wwbn/avideo >=0 <=29.0)

Commands are suggestions: review each one before running it.