CVE-2026-33499: Wwbn/avideo Cross-Site Scripting Vulnerability

MODERATE
Advisory Identifier: GHSA-7292-w8qp-mhq2
CVSS 6.1
CWE-79
Published
Advisory Summary

CVE-2026-33499 is a MODERATE (CVSS 6.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Wwbn/avideo libraries in the Packagist ecosystem. The issue involves avideo has reflected xss via unlockpassword parameter in forbiddenpage.php and warningpage.php. Remediation is available in the latest vendor maintenance releases.

CVE-2026-33499 at a Glance

CVE Identifier CVE-2026-33499
GHSA Identifier GHSA-7292-w8qp-mhq2
Severity MODERATE
CVSS v3.1 Base Score 6.1
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Wwbn/avideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 6.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-33499

To remediate this vulnerability, upgrade all affected Wwbn/avideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wwbn/avideo fixed: Latest secure release
Upgrade wwbn/avideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wwbn/avideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33499, inspect your project dependencies for Wwbn/avideo:

inspect dependencies for wwbn/avideo

Analyze the terminal output to locate any version of Wwbn/avideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Wwbn/avideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The `view/forbiddenPage.php` and `view/warningPage.php` templates reflect the `$_REQUEST['unlockPassword']` parameter directly into an HTML `<input>` tag's attributes without any output encoding or sanitization. An attacker can craft a URL that breaks out of the `value` attribute and injects arbitrary HTML attributes including JavaScript event handlers, achieving reflected XSS against any visitor who clicks the link. ## Details When a user visits a password-protected channel, `view/channel.php:22` calls: ```php forbiddenPage('This channel is password protected', false, $channelPassword); ``` The `forbiddenPage()` function in `objects/functionsSecurity.php:520` checks whether the supplied password matches. If it doesn't (or no password was submitted), it includes `view/forbiddenPage.php` at line 561. In `view/forbiddenPage.php:31-35`, the raw request parameter is reflected into HTML: ```php $value = ''; if (!empty($_REQUEST['unlockPassword'])) { $value = $_REQUEST['unlockPassword']; // Line 33: unsanitized user input } echo getInputPassword('unlockPassword', 'class="form-control" value="' . $value . '"', __('Unlock Password')); ``` The `getInputPassword()` function at `objects/functions.php:4490` outputs the `$attributes` string directly into the `<input>` tag at line 4502: ```php <input id="<?php echo $id; ?>" name="<?php echo $id; ?>" type="password" placeholder="<?php echo $placeholder; ?>" <?php echo $attributes; ?>> ``` The `unlockPassword` parameter is **not listed** in any of the security filter arrays defined in `objects/security.php:4-8` (`$securityFilter`, `$securityFilterInt`, `$securityRemoveSingleQuotes`, `$securityRemoveNonChars`, `$securityRemoveNonCharsStrict`, `$filterURL`), so it passes through the global input sanitization completely unfiltered. Commit `3933d4abc` added sanitization only for the server-side password **comparison** in `functionsSecurity.php:529` (`preg_replace('/[^0-9a-z]/i', '', ...)`), but did not address the client-side reflection in the view templates. The identical vulnerability exists in `view/warningPage.php:31-34`. ## PoC **Step 1:** Identify a password-protected channel (or any page that triggers `forbiddenPage()` with an `$unlockPassword`). **Step 2:** Craft a URL with a malicious `unlockPassword` parameter that breaks out of the `value` attribute: ``` https://target.com/channel/someuser?unlockPassword=" autofocus onfocus="alert(document.cookie) ``` **Step 3:** The server renders the following HTML: ```html <input id="unlockPassword" name="unlockPassword" type="password" placeholder="Unlock Password" class="form-control" value="" autofocus onfocus="alert(document.cookie)"> ``` The `autofocus` attribute causes the browser to immediately focus the input element on page load, triggering the `onfocus` event handler which executes the attacker-controlled JavaScript. No further user interaction is required beyond clicking the link. **Step 4:** The JavaScript executes in the context of the target domain, with access to cookies (no CSP or HttpOnly protections were observed), DOM, and the ability to make authenticated requests on behalf of the victim. ## Impact - **Session hijacking**: An attacker can steal `PHPSESSID` cookies and impersonate any user (including administrators) who clicks the crafted link. - **Account takeover**: The injected JavaScript can change the victim's email/password by submitting forms to the application's account settings endpoints. - **Phishing**: The attacker can overlay fake login forms or redirect users to credential harvesting pages. - **No authentication required**: The vulnerable page is specifically shown to unauthenticated/unauthorized users, making the attack surface broad. ## Recommended Fix Apply `htmlspecialchars()` output encoding to the reflected value in both `view/forbiddenPage.php` and `view/warningPage.php`: **view/forbiddenPage.php** — change line 33: ```php // Before (vulnerable): $value = $_REQUEST['unlockPassword']; // After (fixed): $value = htmlspecialchars($_REQUEST['unlockPassword'], ENT_QUOTES, 'UTF-8'); ``` **view/warningPage.php** — change line 32: ```php // Before (vulnerable): $value = $_REQUEST['unlockPassword']; // After (fixed): $value = htmlspecialchars($_REQUEST['unlockPassword'], ENT_QUOTES, 'UTF-8'); ``` Alternatively, add `'unlockPassword'` to the `$securityFilter` array in `objects/security.php:4` to apply the global XSS filter, though explicit output encoding at the point of use is the more robust defense-in-depth approach.

CVE-2026-33499 Affected Wwbn/avideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
wwbn/avideo
Packagist
≤ 26.0

References

Frequently Asked Questions

What is CVE-2026-33499?
CVE-2026-33499 is a security vulnerability in Wwbn/avideo involving AVideo has Reflected XSS via unlockPassword Parameter in forbiddenPage.php and warningPage.php under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Wwbn/avideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: wwbn/avideo.
What version fixes CVE-2026-33499?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is wwbn/avideo affected?
Yes, wwbn/avideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-33499?
CVE-2026-33499 has a CVSS v3.1 base score of 6.1 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-33499?
CVE-2026-33499 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for CVE-2026-33499?
Run the dependency tree command: 'inspect dependencies for wwbn/avideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7292-w8qp-mhq2",
  "modified" : "2026-03-25T20:31:25Z",
  "published" : "2026-03-20T20:56:38Z",
  "aliases" : [ "CVE-2026-33499" ],
  "summary" : "AVideo has Reflected XSS via unlockPassword Parameter in forbiddenPage.php and warningPage.php",
  "details" : "## Summary\n\nThe `view/forbiddenPage.php` and `view/warningPage.php` templates reflect the `$_REQUEST['unlockPassword']` parameter directly into an HTML `<input>` tag's attributes without any output encoding or sanitization. An attacker can craft a URL that breaks out of the `value` attribute and injects arbitrary HTML attributes including JavaScript event handlers, achieving reflected XSS against any visitor who clicks the link.\n\n## Details\n\nWhen a user visits a password-protected channel, `view/channel.php:22` calls:\n```php\nforbiddenPage('This channel is password protected', false, $channelPassword);\n```\n\nThe `forbiddenPage()` function in `objects/functionsSecurity.php:520` checks whether the supplied password matches. If it doesn't (or no password was submitted), it includes `view/forbiddenPage.php` at line 561.\n\nIn `view/forbiddenPage.php:31-35`, the raw request parameter is reflected into HTML:\n```php\n$value = '';\nif (!empty($_REQUEST['unlockPassword'])) {\n    $value = $_REQUEST['unlockPassword'];  // Line 33: unsanitized user input\n}\necho getInputPassword('unlockPassword', 'class=\"form-control\" value=\"' . $value . '\"', __('Unlock Password'));\n```\n\nThe `getInputPassword()` function at `objects/functions.php:4490` outputs the `$attributes` string directly into the `<input>` tag at line 4502:\n```php\n<input id=\"<?php echo $id; ?>\" name=\"<?php echo $id; ?>\" type=\"password\" placeholder=\"<?php echo $placeholder; ?>\" <?php echo $attributes; ?>>\n```\n\nThe `unlockPassword` parameter is **not listed** in any of the security filter arrays defined in `objects/security.php:4-8` (`$securityFilter`, `$securityFilterInt`, `$securityRemoveSingleQuotes`, `$securityRemoveNonChars`, `$securityRemoveNonCharsStrict`, `$filterURL`), so it passes through the global input sanitization completely unfiltered.\n\nCommit `3933d4abc` added sanitization only for the server-side password **comparison** in `functionsSecurity.php:529` (`preg_replace('/[^0-9a-z]/i', '', ...)`), but did not address the client-side reflection in the view templates.\n\nThe identical vulnerability exists in `view/warningPage.php:31-34`.\n\n## PoC\n\n**Step 1:** Identify a password-protected channel (or any page that triggers `forbiddenPage()` with an `$unlockPassword`).\n\n**Step 2:** Craft a URL with a malicious `unlockPassword` parameter that breaks out of the `value` attribute:\n\n```\nhttps://target.com/channel/someuser?unlockPassword=\" autofocus onfocus=\"alert(document.cookie)\n```\n\n**Step 3:** The server renders the following HTML:\n\n```html\n<input id=\"unlockPassword\" name=\"unlockPassword\" type=\"password\"\n  placeholder=\"Unlock Password\"\n  class=\"form-control\" value=\"\" autofocus onfocus=\"alert(document.cookie)\">\n```\n\nThe `autofocus` attribute causes the browser to immediately focus the input element on page load, triggering the `onfocus` event handler which executes the attacker-controlled JavaScript. No further user interaction is required beyond clicking the link.\n\n**Step 4:** The JavaScript executes in the context of the target domain, with access to cookies (no CSP or HttpOnly protections were observed), DOM, and the ability to make authenticated requests on behalf of the victim.\n\n## Impact\n\n- **Session hijacking**: An attacker can steal `PHPSESSID` cookies and impersonate any user (including administrators) who clicks the crafted link.\n- **Account takeover**: The injected JavaScript can change the victim's email/password by submitting forms to the application's account settings endpoints.\n- **Phishing**: The attacker can overlay fake login forms or redirect users to credential harvesting pages.\n- **No authentication required**: The vulnerable page is specifically shown to unauthenticated/unauthorized users, making the attack surface broad.\n\n## Recommended Fix\n\nApply `htmlspecialchars()` output encoding to the reflected value in both `view/forbiddenPage.php` and `view/warningPage.php`:\n\n**view/forbiddenPage.php** — change line 33:\n```php\n// Before (vulnerable):\n$value = $_REQUEST['unlockPassword'];\n\n// After (fixed):\n$value = htmlspecialchars($_REQUEST['unlockPassword'], ENT_QUOTES, 'UTF-8');\n```\n\n**view/warningPage.php** — change line 32:\n```php\n// Before (vulnerable):\n$value = $_REQUEST['unlockPassword'];\n\n// After (fixed):\n$value = htmlspecialchars($_REQUEST['unlockPassword'], ENT_QUOTES, 'UTF-8');\n```\n\nAlternatively, add `'unlockPassword'` to the `$securityFilter` array in `objects/security.php:4` to apply the global XSS filter, though explicit output encoding at the point of use is the more robust defense-in-depth approach.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wwbn/avideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "26.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-7292-w8qp-mhq2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33499"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/f154167251c9cf183ce09cd018d07e9352310457"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-20T20:56:38Z",
    "nvd_published_at" : "2026-03-23T17:16:51Z"
  }
}