AVideo has an Open Redirect via Unvalidated redirectUri in userLogin.php
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:
var logintimer = setInterval(function() {
if (win.closed) {
clearInterval(logintimer);
document.location = "<?php print $safeRedirectUri; ?>";
}
}, 1000);
The value is printed directly into a JavaScript string literal with no call to json_encode(), 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 them as https://evil.com when embedded in a navigation target. Additional bypass vectors include subdomain confusion of the form https://trusted.com.evil.com and path-prefix matching weaknesses. Because the reflected value lands inside a JavaScript string rather than an HTML attribute, HTML-level encoding would not prevent exploitation either. Once the popup window is closed, the setInterval callback fires every second, and the first time win.closed is truthy the victim's main page is redirected to the attacker's URL.
PoC
https://victim.com/view/userLogin.php?redirectUri=//evil.com
import requests
base = "https://victim.com/view/userLogin.php"
payload = "//evil.com"
r = requests.get(base, params={"redirectUri": payload})
assert payload in r.text, "Payload not reflected"
print("Reflected payload found in response")
Impact
An unauthenticated attacker can craft a login URL and distribute it to victims. After the victim interacts with the login popup and closes it, the main page is silently navigated to an attacker-controlled domain. This enables phishing attacks where the victim is presented with a credential-harvesting page that visually mimics the original site. All users of any AVideo installation are potentially affected because no authentication is required to trigger the redirect. The attack requires only that the victim follow the crafted link and complete or dismiss the popup, making it practical in targeted phishing campaigns.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | wwbn/avideo | <= 25.0 | no fix |
References
- CVSS vector
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- Weakness (CWE)
CWE-601- Platform
- Composer
- Package
wwbn/avideo- Disclosed
- 19.03.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-hj5h-5623-gwhw - CC BY 4.0
Vulnerability history: wwbn/avideo
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 160
- First → latest
- 04.2022 06.2026
- Without a fix
- 143
- Exploited in attacks
- 0
Severity breakdown
- Critical 14
- High 61
- Medium 83
- Low 2
Disclosures per year
- 2022: 2
- 2023: 5
- 2024: 5
- 2025: 0
- 2026: 148
-
AVideo has an Open Redirect via Unvalidated redirectUri in userLogin.php this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.