AVideo has an Open Redirect via Unvalidated redirectUri in userLogin.php

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2026-33296: 0.19% estimated exploitation activity in the next 30 days; percentile 9.09 (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 WWBN/AVideo contains an open redirect vulnerability in the login flow where a user-supplied redirectUri parameter is reflected directly into a JavaScript document.location assignment without JavaScript-safe encoding. After a user completes the login popup flow, a timer callback executes the redirect using the unvalidated value, sending the victim to an attacker-controlled site. Details In view/userLogin.php, the application accepts a redirectUri GET parameter, passes it through a function called isSafeRedirectURL(), and stores the result in $safeRedirectUri. This value is then embedded into an inline JavaScript block: The value is printed directly into a JavaScript string literal with no call to jsonencode(), htmlspecialchars(), or any JavaScript-context escaping. Even if isSafeRedirectURL() is intended to filter dangerous values, protocol-relative URLs such as //evil.com satisfy many naive URL validation checks because they carry no explicit scheme, yet browsers will resolve…

Published by the source

19 Mar 2026, 17:25 UTC

Last modified by the source

25 Mar 2026, 18:34 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hj5h-5623-gwhw

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

# Patch Next advisory brief: CVE-2026-33296

Advisory: AVideo has an Open Redirect via Unvalidated redirectUri in userLogin.php
IDs: CVE-2026-33296, GHSA-hj5h-5623-gwhw
Record: https://patchnext.com/advisories/cve-2026-33296 (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: Low (CVSS 2.1)
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 <= 25.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-hj5h-5623-gwhw (GitHub-reviewed advisory GHSA-hj5h-5623-gwhw lists affected ranges: Packagist wwbn/avideo >=0 <=25.0)

Commands are suggestions: review each one before running it.