Summary
CVE-2026-82644 is a rate-limiting bypass vulnerability in WWBN AVideo that allows unauthenticated attackers to perform unrestricted password-guessing attacks against the login endpoint and 13 other sensitive endpoints. The flaw stems from the application’s bot-detection logic silently discarding brute-force attempt counters for requests it classifies as bot traffic, effectively disabling the protection for any attacker who omits or spoofs their User-Agent header. The issue carries a CVSS v4.0 base score of 8.7 (High).
Technical details
- Root cause: the
enforceRateLimit()function stores its attempt counter through a caching layer (ObjectYPT::setCacheGlobal) that silently discards writes whenever the request is classified as bot traffic by theisBot()function. isBot()treats a missingUser-Agentheader as bot traffic by default, and also matches common bot identifiers such ascurl,bot,crawler, andspider.- Because the counter never increments for such clients, the rate limit never triggers, regardless of how many requests are sent.
- Attack vector: network, unauthenticated, no user interaction required — an attacker simply omits the
User-Agentheader (or uses a default tool User-Agent likecurl‘s) when sending requests. - Impact: unrestricted, automatable password-guessing (brute-force) attacks against
login.json.phpand at least 13 other endpoints that rely on the same rate-limiting function, threatening account confidentiality/takeover.
Affected software
- WWBN AVideo — current development version at commit
e01e41eccand all earlier versions (no version boundary specified by the advisory; all releases relying onenforceRateLimit()are affected).
Severity
- CVSS v4.0 Base Score: 8.7 (High) —
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N - CVSS v3.1 Base Score: 7.5 (High) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate: No official patched release/commit is currently available from the vendor at time of publication; a community-proposed fix (introducing an
$ignoreBotflag so rate-limit counters bypass bot-filtering while page-cache behavior is preserved) has been submitted but not yet merged. Monitor the vendor repository for an official fix and upgrade as soon as one is released. - Workarounds/network mitigations until a patch is available:
- Enforce rate limiting and brute-force protection at the network/edge layer (WAF, reverse proxy, or API gateway) independent of the application’s own logic, ensuring it does not exempt requests with missing or bot-like User-Agent headers.
- Monitor and alert on high-volume login/authentication attempts from clients with missing or generic User-Agent strings (e.g.,
curl, blank,bot). - Consider enforcing multi-factor authentication and strong password policies to reduce the impact of successful brute-force attempts.
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(

