/

CVE-2026-92578

Severity:

HIGH RISK

(8.1)

Authentication Bypass (CWE-287) in WWBN AVideo Login

CVE-2026-92578

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Account Takeover

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

WWBN AVideo contains an authentication bypass that treats a user's stored password hash as an acceptable login credential through multiple authentication paths. An attacker who obtains a users.password hash may authenticate as that user without knowing the original password, potentially taking over accounts.

Affected context

The vulnerability occurs in WWBN AVideo deployments through version 29.0 when login requests are processed by authentication logic that accepts stored password hashes as valid credentials. Risk is present when an attacker can obtain password-hash data through database exposure, backups, logs, insufficient access controls, or another prior compromise.

Exploit preconditions

  • Attack surface: AVideo login endpoints and authentication request handlers
  • Required access: Access to a target user's stored password hash
  • Trigger point: Authentication processing through loginFromRequest() or encryptPasswordVerify()
  • Why exploitation is possible: The authentication logic can compare or accept the stored hash as though it were the user's password, allowing credential verification to be bypassed

Why this happens

The underlying flaw is an authentication design error in which a password representation intended only for secure storage is also accepted as an authentication credential. This breaks the separation between password verification data and user-supplied login secrets. The behavior maps to CWE-287: Improper Authentication, because the application does not reliably establish that the requester knows the original password before granting access.

Potential impact

  • Attackers may authenticate as affected users
  • Administrative or privileged accounts could be taken over
  • Unauthorized users could access private videos, profiles, or account data
  • Attackers could modify content, settings, or user information
  • Compromised accounts could be used for further attacks against the application

General mitigation guidance

Mitigation generally focuses on ensuring that only the original password, or a securely managed alternative authentication factor, can satisfy login verification.

Common defensive patterns include:

  • Keep password hashes exclusively as verification artifacts and never accept them as login secrets
  • Use well-tested password verification functions that compare a supplied password against the stored hash without reversing or exposing the hash
  • Centralize authentication logic so every login path applies the same verification rules
  • Protect password hashes with strict database, backup, logging, and administrative access controls
  • Apply least privilege to accounts and authentication-related services
  • Consider credential rotation and session invalidation when hash exposure is suspected

How teams detect issues like this

Organizations can assess for this weakness through:

  • Static analysis searches for authentication branches that compare user input directly with stored password hashes
  • Code review of all login handlers, alternate authentication paths, and helper functions
  • Tests confirming that a retrieved password hash cannot be submitted as a valid password
  • Monitoring for unusual successful logins following database, backup, or credential-store access
  • Policy enforcement requiring centralized password verification and prohibiting hash reuse as a credential
  • Automated security review tools that identify inconsistent authentication checks

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-fq38-jp6c-q4cx
vulncheck.comvulncheck.com/advisories/wwbn-avideo-through-29.0-authentication-bypass-via-stored-password-hash

Frequently asked

questions

The login bypass can be exercised through exposed AVideo authentication endpoints, but exploitation generally depends on first obtaining a target user's stored password hash.

An attacker needs access to a valid stored hash. They may not need the user's original password, and the resulting access depends on the privileges associated with the targeted account.

Ensure every authentication path verifies the supplied password using a standard password-hashing verification routine and rejects stored hashes as direct credentials.

Centralize authentication logic, protect credential stores and backups, review alternate login paths, and add tests that confirm password hashes cannot be reused for authentication.

Find out what's already
exploitable in your codebase.