AVideo has Pre-Captcha User Enumeration and Account Status Disclosure in Password Recovery Endpoint

Exploitation

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

CVSS

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

EPSS

• CVE-2026-33688: 0.28% estimated exploitation activity in the next 30 days; percentile 20.91 (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 The password recovery endpoint at objects/userRecoverPass.php performs user existence and account status checks before validating the captcha. This allows an unauthenticated attacker to enumerate valid usernames and determine whether accounts are active, inactive, or banned — at scale and without solving any captcha — by observing three distinct JSON error responses. Details In objects/userRecoverPass.php, the request flow is: 1. Line 11 — A User object is instantiated from unsanitized $REQUEST['user'] with no authentication: 2. Lines 27-29 — If the user does not exist, a distinct error is returned immediately: 3. Lines 31-33 — If the user exists but is not active, a different distinct error is returned: 4. Lines 37-41 — Captcha validation only occurs after both user enumeration checks: This ordering creates a reliable oracle: requests that hit the captcha check confirm the user exists and is active, while the two earlier error messages reveal non-existence or inactive status…

Published by the source

25 Mar 2026, 19:53 UTC

Last modified by the source

25 Mar 2026, 19:53 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m99f-mmvg-3xmx

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

# Patch Next advisory brief: CVE-2026-33688

Advisory: AVideo has Pre-Captcha User Enumeration and Account Status Disclosure in Password Recovery Endpoint
IDs: CVE-2026-33688, GHSA-m99f-mmvg-3xmx
Record: https://patchnext.com/advisories/cve-2026-33688 (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: Medium (CVSS 5.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-m99f-mmvg-3xmx (GitHub-reviewed advisory GHSA-m99f-mmvg-3xmx lists affected ranges: Packagist wwbn/avideo >=0 <=26.0)

Commands are suggestions: review each one before running it.