AVideo has Session Fixation via GET PHPSESSID Parameter With Disabled Login Session Regeneration

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33492: 0.30% estimated exploitation activity in the next 30 days; percentile 22.95 (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 AVideo's sessionstart() 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) The code reads $GET['PHPSESSID'] and programmatically calls sessionid($PHPSESSID), which bypasses both session.useonlycookies and session.usestrictmode PHP settings since the session ID is set via the PHP API, not via cookie/URL handling. 2. Session regeneration bypass for blacklisted endpoints…

Published by the source

20 Mar 2026, 20:49 UTC

Last modified by the source

9 May 2026, 07:39 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x3pr-vrhq-vq43

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

# Patch Next advisory brief: CVE-2026-33492

Advisory: AVideo has Session Fixation via GET PHPSESSID Parameter With Disabled Login Session Regeneration
IDs: CVE-2026-33492, GHSA-x3pr-vrhq-vq43
Record: https://patchnext.com/advisories/cve-2026-33492 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
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 <= 26.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-x3pr-vrhq-vq43 (GitHub-reviewed advisory GHSA-x3pr-vrhq-vq43 lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.