CVE-2026-85154: WWBN AVideo Authentication Bypass via Non-Expiring video_id_hash
WWBN AVideo contains an authentication failure vulnerability where the video_id_hash credential is a non-expiring, non-revocable bearer token that grants full administrator session access to the video owner's account. Attackers who obtain a video_id_hash can replay it indefinitely to authenticate as the video owner with full privileges, and the credential remains valid even after the owner changes their password.
Security readout for executives and security teams
Plain-English summary
AVideo may treat a video-related hash as a permanent login credential. Anyone who obtains one could repeatedly access the video owner’s account with administrator privileges, even after a password change. This could enable data theft, unauthorized changes, service disruption, and persistent account takeover.
Executive priority
Treat as an immediate investigation and remediation priority for exposed AVideo systems. The potential impact is complete privileged account compromise with persistence beyond password changes. Prioritize inventory, containment, vendor guidance review, and evidence preservation; do not assume ordinary password resets remove access.
Technical view
The video_id_hash functions as a non-expiring, non-revocable bearer credential. Reportedly, it can establish a fully privileged session for the video owner without authentication, user interaction, or prior access. Password changes do not invalidate it. The supplied CVSS 3.1 score is 9.8, but the affected version data is incomplete.
Likely exposure
Potential exposure includes AVideo deployments where video_id_hash values are generated, stored, logged, shared, or transmitted and could be obtained by an unauthorized party. Internet-accessible deployments warrant urgent review. The source bundle does not establish a reliable affected version range or confirm whether default installations expose these hashes.
Exploitation context
The credential can reportedly be replayed remotely with low complexity and no privileges or user interaction. However, an attacker must first obtain a valid video_id_hash. The CVE is not listed as KEV in the supplied data, and the provided sources do not establish active exploitation.
Researcher notes
Key review areas are token generation, entropy, transport, persistence, session establishment, authorization mapping, revocation, and logging. Determine whether hashes leak through URLs, referrers, caches, APIs, or shared metadata. The supplied affected-version entry lists version “0” with default status “unaffected,” so version applicability requires confirmation from the advisory or vendor.
Mitigation direction
Review the vendor advisory immediately for fixed versions or official remediation; none is identified in the supplied bundle.
Upgrade to a vendor-confirmed fixed release when available.
Restrict AVideo access and administrative interfaces until remediation is confirmed.
Prevent video_id_hash values from appearing in URLs, logs, analytics, messages, or shared content.
Invalidate affected sessions and credentials using vendor-supported procedures; password changes alone are reportedly insufficient.
Validation and detection
Inventory all AVideo deployments and record their exact versions and internet accessibility.
Compare installed versions and configurations with the vendor advisory’s affected-version guidance.
Review logs and data stores for disclosure or suspicious reuse of video_id_hash values.
Verify that password changes and logout procedures invalidate existing privileged sessions and related hashes.
Confirm remediation prevents old video_id_hash values from creating authenticated administrator sessions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.