CVE-2026-33492: Wwbn/avideo AVideo Has Session Fixation Vulnerability

HIGH
Advisory Identifier: GHSA-x3pr-vrhq-vq43
CVSS 7.3
CWE-384
Published
Advisory Summary

CVE-2026-33492 is a HIGH (CVSS 7.3) avideo has session fixation vulnerability (CWE-384: Session Fixation) affecting Wwbn/avideo libraries in the Packagist ecosystem. The issue involves avideo has session fixation via get phpsessid parameter with disabled login session regeneration. Remediation is available in the latest vendor maintenance releases.

CVE-2026-33492 at a Glance

CVE Identifier CVE-2026-33492
GHSA Identifier GHSA-x3pr-vrhq-vq43
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification CWE-384: Session Fixation
Affected Product Wwbn/avideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.3

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

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

How to Fix CVE-2026-33492

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-33492, 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-384: Session Fixation, where authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. 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 AVideo's `_session_start()` function accepts arbitrary session IDs via the `PHPSESSID` GET parameter and sets them as the active PHP session. A session regeneration bypass exists for specific blacklisted endpoints when the request originates from the same domain. Combined with the explicitly disabled session regeneration in `User::login()`, this allows a classic session fixation attack where an attacker can fix a victim's session ID before authentication and then hijack the authenticated session. ## Details The vulnerability is a chain of three weaknesses that together enable session fixation: ### 1. Attacker-controlled session ID acceptance (`objects/functionsPHP.php:344-367`) ```php function _session_start(array $options = []) { // ... if (isset($_GET['PHPSESSID']) && !_empty($_GET['PHPSESSID'])) { $PHPSESSID = $_GET['PHPSESSID']; // ... if (!User::isLogged()) { if ($PHPSESSID !== session_id()) { _session_write_close(); session_id($PHPSESSID); // <-- sets session to attacker's ID } $session = @session_start($options); // <-- starts with attacker's ID ``` The code reads `$_GET['PHPSESSID']` and programmatically calls `session_id($PHPSESSID)`, which bypasses both `session.use_only_cookies` and `session.use_strict_mode` PHP settings since the session ID is set via the PHP API, not via cookie/URL handling. ### 2. Session regeneration bypass for blacklisted endpoints (`objects/functionsPHP.php:375-378`, `objects/functions.php:3100-3116`) ```php // functionsPHP.php:375-378 if (!blackListRegenerateSession()) { _session_regenerate_id(); // <-- SKIPPED when blacklisted + same-domain } ``` ```php // functions.php:3100-3116 function blackListRegenerateSession() { if (!requestComesFromSafePlace()) { return false; } $list = [ 'objects/getCaptcha.php', 'objects/userCreate.json.php', 'objects/videoAddViewCount.json.php', ]; foreach ($list as $needle) { if (str_ends_with($_SERVER['SCRIPT_NAME'], $needle)) { return true; // <-- regeneration skipped for these endpoints } } return false; } ``` The `requestComesFromSafePlace()` check at `objects/functionsSecurity.php:182` only verifies that `HTTP_REFERER` matches the AVideo domain. When a victim clicks a link from within the AVideo platform (e.g., in a comment or video description), the browser naturally sets the Referer to the AVideo domain, satisfying this check. ### 3. Disabled session regeneration on login (`objects/user.php:1315-1317`) ```php // Call custom session regenerate logic // this was regenerating the session all the time, making harder to save info in the session //_session_regenerate_id(); // <-- COMMENTED OUT ``` The session regeneration after authentication is explicitly disabled. This means the session ID persists unchanged through the login transition, which is the fundamental requirement for session fixation to succeed. ### Amplifying factors - `objects/phpsessionid.json.php` exposes session IDs to any same-origin JavaScript without authentication (line 12: `$obj->phpsessid = session_id()`) - `view/js/session.js` stores the session ID in a global `window.PHPSESSID` variable and logs it to console (line 15) - No session-to-IP or session-to-user-agent binding exists (verified via codebase search) ## PoC ### Step 1: Attacker obtains a session ID ```bash # Attacker visits the site to get a valid session ID curl -v https://target.example.com/ 2>&1 | grep 'set-cookie.*PHPSESSID' # Response: Set-Cookie: PHPSESSID=attacker_known_session_id; ... ``` ### Step 2: Attacker injects a link on the platform The attacker posts a comment on a video or creates content containing a link: ``` https://target.example.com/objects/getCaptcha.php?PHPSESSID=attacker_known_session_id ``` This can be placed in a video comment, video description, user bio, or forum post — anywhere AVideo renders user-provided links. ### Step 3: Victim clicks the link while browsing AVideo When the victim clicks the link from within the AVideo platform: 1. Browser sets `Referer: https://target.example.com/...` (same-domain) 2. `_session_start()` processes `$_GET['PHPSESSID']`, victim is not logged in, so `session_id('attacker_known_session_id')` is called 3. `blackListRegenerateSession()` returns `true` (script is `getCaptcha.php` + same-domain Referer) 4. `_session_regenerate_id()` is **skipped** 5. Victim's session is now fixed to `attacker_known_session_id` ### Step 4: Victim logs in The victim navigates to the login page and authenticates. `User::login()` populates `$_SESSION['user']` but does NOT regenerate the session ID (line 1317 is commented out). ### Step 5: Attacker hijacks the authenticated session ```bash # Attacker uses the known session ID to access victim's account curl -b "PHPSESSID=attacker_known_session_id" https://target.example.com/objects/user.php?userAPI=1 # Response: victim's user data, confirming session hijack ``` ## Impact - **Full account takeover**: An attacker can hijack any user's authenticated session, including administrator accounts - **Data access**: Full access to the victim's videos, private content, messages, and personal information - **Privilege escalation**: If the victim is an admin, the attacker gains full administrative control over the AVideo instance - **Lateral actions**: The attacker can perform any action as the victim — upload/delete content, modify settings, access admin panel ## Recommended Fix ### Fix 1: Re-enable session regeneration on login (`objects/user.php:1317`) ```php // Replace the commented-out line: //_session_regenerate_id(); // With: _session_regenerate_id(); ``` This is the most critical fix. Session regeneration on authentication transition is a fundamental defense against session fixation (OWASP recommendation). ### Fix 2: Remove GET-based session ID acceptance (`objects/functionsPHP.php:344-383`) Remove or restrict the `$_GET['PHPSESSID']` handling entirely. If it is needed for specific use cases (e.g., CAPTCHA), validate the session ID against a server-side token rather than blindly accepting arbitrary values: ```php // Instead of accepting any GET PHPSESSID, remove this block entirely. // If CAPTCHA requires session continuity, pass a CSRF token instead. if (isset($_GET['PHPSESSID']) && !_empty($_GET['PHPSESSID'])) { // REMOVED: Do not accept session IDs from URL parameters } ``` ### Fix 3: Remove session ID exposure (`objects/phpsessionid.json.php`, `view/js/session.js`) The `phpsessionid.json.php` endpoint and the `session.js` global variable negate the `httponly` cookie flag. If JavaScript needs to reference the session for AJAX requests, the browser automatically includes session cookies — there is no need to expose the session ID value to JavaScript.

CVE-2026-33492 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-33492?
CVE-2026-33492 is a security vulnerability in Wwbn/avideo involving AVideo has Session Fixation via GET PHPSESSID Parameter With Disabled Login Session Regeneration under CWE-384: Session Fixation.
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-33492?
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-33492?
CVE-2026-33492 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-33492?
CVE-2026-33492 is classified under CWE-384: Session Fixation (Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.).
How can I check Packagist dependencies for CVE-2026-33492?
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-x3pr-vrhq-vq43",
  "modified" : "2026-03-25T20:31:06Z",
  "published" : "2026-03-20T20:49:23Z",
  "aliases" : [ "CVE-2026-33492" ],
  "summary" : "AVideo has Session Fixation via GET PHPSESSID Parameter With Disabled Login Session Regeneration",
  "details" : "## Summary\n\nAVideo's `_session_start()` function accepts arbitrary session IDs via the `PHPSESSID` GET parameter and sets them as the active PHP session. A session regeneration bypass exists for specific blacklisted endpoints when the request originates from the same domain. Combined with the explicitly disabled session regeneration in `User::login()`, this allows a classic session fixation attack where an attacker can fix a victim's session ID before authentication and then hijack the authenticated session.\n\n## Details\n\nThe vulnerability is a chain of three weaknesses that together enable session fixation:\n\n### 1. Attacker-controlled session ID acceptance (`objects/functionsPHP.php:344-367`)\n\n```php\nfunction _session_start(array $options = [])\n{\n    // ...\n    if (isset($_GET['PHPSESSID']) && !_empty($_GET['PHPSESSID'])) {\n        $PHPSESSID = $_GET['PHPSESSID'];\n        // ...\n        if (!User::isLogged()) {\n            if ($PHPSESSID !== session_id()) {\n                _session_write_close();\n                session_id($PHPSESSID);   // <-- sets session to attacker's ID\n            }\n            $session = @session_start($options);  // <-- starts with attacker's ID\n```\n\nThe code reads `$_GET['PHPSESSID']` and programmatically calls `session_id($PHPSESSID)`, which bypasses both `session.use_only_cookies` and `session.use_strict_mode` PHP settings since the session ID is set via the PHP API, not via cookie/URL handling.\n\n### 2. Session regeneration bypass for blacklisted endpoints (`objects/functionsPHP.php:375-378`, `objects/functions.php:3100-3116`)\n\n```php\n// functionsPHP.php:375-378\nif (!blackListRegenerateSession()) {\n    _session_regenerate_id();  // <-- SKIPPED when blacklisted + same-domain\n}\n```\n\n```php\n// functions.php:3100-3116\nfunction blackListRegenerateSession()\n{\n    if (!requestComesFromSafePlace()) {\n        return false;\n    }\n    $list = [\n        'objects/getCaptcha.php',\n        'objects/userCreate.json.php',\n        'objects/videoAddViewCount.json.php',\n    ];\n    foreach ($list as $needle) {\n        if (str_ends_with($_SERVER['SCRIPT_NAME'], $needle)) {\n            return true;  // <-- regeneration skipped for these endpoints\n        }\n    }\n    return false;\n}\n```\n\nThe `requestComesFromSafePlace()` check at `objects/functionsSecurity.php:182` only verifies that `HTTP_REFERER` matches the AVideo domain. When a victim clicks a link from within the AVideo platform (e.g., in a comment or video description), the browser naturally sets the Referer to the AVideo domain, satisfying this check.\n\n### 3. Disabled session regeneration on login (`objects/user.php:1315-1317`)\n\n```php\n// Call custom session regenerate logic\n// this was regenerating the session all the time, making harder to save info in the session\n//_session_regenerate_id();  // <-- COMMENTED OUT\n```\n\nThe session regeneration after authentication is explicitly disabled. This means the session ID persists unchanged through the login transition, which is the fundamental requirement for session fixation to succeed.\n\n### Amplifying factors\n\n- `objects/phpsessionid.json.php` exposes session IDs to any same-origin JavaScript without authentication (line 12: `$obj->phpsessid = session_id()`)\n- `view/js/session.js` stores the session ID in a global `window.PHPSESSID` variable and logs it to console (line 15)\n- No session-to-IP or session-to-user-agent binding exists (verified via codebase search)\n\n## PoC\n\n### Step 1: Attacker obtains a session ID\n\n```bash\n# Attacker visits the site to get a valid session ID\ncurl -v https://target.example.com/ 2>&1 | grep 'set-cookie.*PHPSESSID'\n# Response: Set-Cookie: PHPSESSID=attacker_known_session_id; ...\n```\n\n### Step 2: Attacker injects a link on the platform\n\nThe attacker posts a comment on a video or creates content containing a link:\n\n```\nhttps://target.example.com/objects/getCaptcha.php?PHPSESSID=attacker_known_session_id\n```\n\nThis can be placed in a video comment, video description, user bio, or forum post — anywhere AVideo renders user-provided links.\n\n### Step 3: Victim clicks the link while browsing AVideo\n\nWhen the victim clicks the link from within the AVideo platform:\n1. Browser sets `Referer: https://target.example.com/...` (same-domain)\n2. `_session_start()` processes `$_GET['PHPSESSID']`, victim is not logged in, so `session_id('attacker_known_session_id')` is called\n3. `blackListRegenerateSession()` returns `true` (script is `getCaptcha.php` + same-domain Referer)\n4. `_session_regenerate_id()` is **skipped**\n5. Victim's session is now fixed to `attacker_known_session_id`\n\n### Step 4: Victim logs in\n\nThe victim navigates to the login page and authenticates. `User::login()` populates `$_SESSION['user']` but does NOT regenerate the session ID (line 1317 is commented out).\n\n### Step 5: Attacker hijacks the authenticated session\n\n```bash\n# Attacker uses the known session ID to access victim's account\ncurl -b \"PHPSESSID=attacker_known_session_id\" https://target.example.com/objects/user.php?userAPI=1\n# Response: victim's user data, confirming session hijack\n```\n\n## Impact\n\n- **Full account takeover**: An attacker can hijack any user's authenticated session, including administrator accounts\n- **Data access**: Full access to the victim's videos, private content, messages, and personal information\n- **Privilege escalation**: If the victim is an admin, the attacker gains full administrative control over the AVideo instance\n- **Lateral actions**: The attacker can perform any action as the victim — upload/delete content, modify settings, access admin panel\n\n## Recommended Fix\n\n### Fix 1: Re-enable session regeneration on login (`objects/user.php:1317`)\n\n```php\n// Replace the commented-out line:\n//_session_regenerate_id();\n\n// With:\n_session_regenerate_id();\n```\n\nThis is the most critical fix. Session regeneration on authentication transition is a fundamental defense against session fixation (OWASP recommendation).\n\n### Fix 2: Remove GET-based session ID acceptance (`objects/functionsPHP.php:344-383`)\n\nRemove or restrict the `$_GET['PHPSESSID']` handling entirely. If it is needed for specific use cases (e.g., CAPTCHA), validate the session ID against a server-side token rather than blindly accepting arbitrary values:\n\n```php\n// Instead of accepting any GET PHPSESSID, remove this block entirely.\n// If CAPTCHA requires session continuity, pass a CSRF token instead.\nif (isset($_GET['PHPSESSID']) && !_empty($_GET['PHPSESSID'])) {\n    // REMOVED: Do not accept session IDs from URL parameters\n}\n```\n\n### Fix 3: Remove session ID exposure (`objects/phpsessionid.json.php`, `view/js/session.js`)\n\nThe `phpsessionid.json.php` endpoint and the `session.js` global variable negate the `httponly` cookie flag. If JavaScript needs to reference the session for AJAX requests, the browser automatically includes session cookies — there is no need to expose the session ID value to JavaScript.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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-x3pr-vrhq-vq43"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33492"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/5647a94d79bf69a972a86653fe02144079948785"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-384" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-20T20:49:23Z",
    "nvd_published_at" : "2026-03-23T16:16:49Z"
  }
}