CVE-2026-82644: Improper Restriction of Excessive Authentication Attempts in WWBN AVideo
Description
WWBN AVideo (current e01e41ecc and earlier) contains a brute-force rate limiting bypass in enforceRateLimit(), which protects login.json.php and 13 other endpoints. The function stores its attempt counter via a cache layer (ObjectYPT::setCacheGlobal) that silently discards writes for any client identified as a bot by isBot(). Because isBot() treats a missing User-Agent header as a bot by default — and also matches common bot identifiers such as 'curl', 'bot', 'crawler', and 'spider' — the counter never increments for such clients, so the rate limit never fires. An unauthenticated attacker can therefore submit unlimited login attempts (e.g., by omitting the User-Agent header or using curl's default User-Agent), enabling unrestricted password-guessing attacks.
CVSS v4.0
Score 8.7high
Affected software
WWBN
AVideo
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-82644 describes a brute-force rate limiting bypass in WWBN AVideo's enforceRateLimit() function, which protects login.json.php and 13 other endpoints. The function uses a cache layer to track authentication attempts but silently discards writes for clients identified as bots by the isBot() function. Since isBot() treats missing User-Agent headers and common bot strings (e.g., 'curl', 'bot', 'crawler', 'spider') as bots, the attempt counter never increments for such clients. Consequently, the rate limit never triggers, allowing unauthenticated attackers to perform unlimited login attempts and password guessing attacks.
Potential Impact
An unauthenticated attacker can bypass the brute-force rate limiting protections by omitting or manipulating the User-Agent header to appear as a bot. This allows unlimited login attempts against the affected endpoints, increasing the risk of successful password guessing and unauthorized access. The vulnerability affects authentication security but does not indicate direct code execution or data exposure beyond authentication bypass.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider implementing additional protections such as stricter rate limiting that does not rely on User-Agent headers or bot detection, and monitoring for unusual login attempt patterns. Avoid relying solely on User-Agent-based bot detection for security controls.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-30T13:38:00.101Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a944043acd9273b49a612a6
Added to database: 08/30/2026, 14:37:55 UTC
Last enriched: 09/07/2026, 14:58:48 UTC
Last updated: 10/15/2026, 18:48:24 UTC
Views: 114
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.