Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82644 – Authentication Rate-Limit Bypass (Brute-Force) – WWBN AVideo ≤ commit e01e41ecc (al

Be the first to know when new zero-days emerge:

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 the isBot() function.
  • isBot() treats a missing User-Agent header as bot traffic by default, and also matches common bot identifiers such as curl, bot, crawler, and spider.
  • 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-Agent header (or uses a default tool User-Agent like curl‘s) when sending requests.
  • Impact: unrestricted, automatable password-guessing (brute-force) attacks against login.json.php and 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 e01e41ecc and all earlier versions (no version boundary specified by the advisory; all releases relying on enforceRateLimit() 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 $ignoreBot flag 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(

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge