Summary
CVE-2026-84479 is an authentication bypass by spoofing vulnerability (CWE-290) in WWBN AVideo. Three login-time security controls — two-factor authentication, CAPTCHA/brute-force throttling, and login/device audit logging — are enforced solely by checking the client-supplied User-Agent HTTP header, allowing an attacker with valid credentials to bypass all three simply by changing that header. The issue is rated CRITICAL with a CVSS score of 9.3.
Technical details
- Root cause: the
isAVideoEncoder()andisAVideoMobileApp()functions determine trusted-client status by matching theHTTP_USER_AGENTrequest header against hardcoded literal strings (AVideoEncoder,AVideoMobileApp), with no IP address verification and no shared-secret/token validation. - Trigger condition: an attacker who already possesses valid account credentials submits a login request with the
User-Agentheader set toAVideoEncoder(orAVideoMobileApp). - Attack vector: network, no user interaction required, low attack complexity, no elevated privileges needed beyond valid credentials.
- Impact: two-factor authentication is skipped, CAPTCHA/brute-force escalation is bypassed, and the login is not recorded in login/device audit history — undermining account security controls and audit trails.
Affected software
- WWBN AVideo — versions up to and including 29.0 (no fixed version available at time of publication)
Severity
- CVSS v3.1 Base Score: 9.1 (Critical) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - CVSS v4.0 Base Score: 9.3 (Critical) —
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
Mitigation and recommended actions
- Immediate: No patched version is available at the time of publication; monitor the vendor’s repository and advisories for a fix and apply it as soon as it is released.
- Workarounds: Restrict or monitor login endpoints for requests using the
AVideoEncoder/AVideoMobileAppUser-Agent strings at a reverse proxy or WAF, since this header alone should not be trusted to bypass 2FA/CAPTCHA. Enforce IP allow-listing for legitimate encoder/mobile app clients where possible, and review login/audit logs for anomalies that may indicate this header was used to bypass logging.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Page title:
Sign In - AVideo,AVideo - Raw response body:
id="avideoModal",avideoAlert(,avideoModalIframe(

