Security readout for executives and security teams
Plain-English summary
AVideo trusts an easily changed browser identifier during login. An attacker who already has valid credentials can impersonate an approved encoder and bypass two-factor authentication, captcha escalation, and login/device auditing. This increases account-takeover impact and reduces defenders’ ability to detect it. No patch was available when the advisory was published.
Executive priority
Treat this as an urgent credential-compromise amplifier. Prioritize internet-facing and privileged AVideo deployments, apply compensating access controls now, and assign ownership for monitoring vendor updates. The lack of a published patch and the ability to evade MFA and local audit history justify immediate action, despite no supplied evidence of active exploitation.
Technical view
In WWBN AVideo through commit e01e41ecc, isAVideoEncoder() and isAVideoMobileApp() compare HTTP_USER_AGENT with hardcoded values without cryptographic authentication, a shared secret, or an IP check. Supplying the encoder identifier with valid credentials bypasses three login-time controls. The issue is classified as CWE-290 and scored CVSS 4.0 9.3.
Likely exposure
Internet-accessible AVideo login endpoints are the primary concern, especially where credentials may be stolen, reused, or shared. The supplied data identifies current e01e41ecc and earlier as affected, although its structured version field is ambiguous. Confirm deployed commits directly rather than relying on the value “0.”
Exploitation context
The supplied sources describe a low-complexity, network-reachable bypass requiring valid credentials. They do not establish active exploitation, and the CVE is not identified as being in KEV. Successful abuse could defeat MFA and anti-brute-force controls while suppressing relevant login/device audit records, making credential misuse harder to identify.
Researcher notes
The flaw is a trust-boundary failure: attacker-controlled HTTP_USER_AGENT is treated as proof of a trusted client. Validation should remain defensive and authorized. Evidence supports bypass of MFA, captcha escalation, and device/login recording, but not passwordless access. The bundle’s version metadata is inconsistent, so commit-level verification and vendor clarification are important.
Mitigation direction
- Check WWBN guidance frequently and apply an official correction immediately when available.
- Restrict AVideo login access to trusted networks or an authenticated access gateway where operationally feasible.
- Enforce independent upstream authentication that does not trust the client-supplied User-Agent header.
- Reset exposed or reused credentials and review administrator account access.
- Increase monitoring outside AVideo because affected login auditing may be bypassed.
Validation and detection
- Inventory AVideo deployments, exposed login endpoints, and deployed commit identifiers.
- Determine whether each deployment is e01e41ecc or earlier.
- Review proxy, identity-provider, and network logs for suspicious successful logins or encoder User-Agent claims.
- Confirm compensating access controls protect every reachable AVideo login path.
- Recheck the vendor advisory for patch availability and updated affected-version guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupCredential and access behavior lookup
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.
Open ATT&CK lookupCVE-2026-84479 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-m9m3-gwh2-337c)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: WWBN AVideo Authentication Bypass via User-Agent HeaderCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.