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

Back
New CVE Detected

CVE-2026-84476 – Authentication/Rate-Limit Bypass – WWBN AVideo ≤ 29.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-84476 is an authentication bypass vulnerability (CWE-290) in WWBN AVideo. The application’s login rate-limiting function trusts client IP addresses taken from the X-Real-IP and X-Forwarded-For headers without verifying that the request actually passed through a trusted proxy, allowing an unauthenticated network attacker to spoof their apparent source address. This lets an attacker bypass login throttling and perform unlimited credential-guessing attacks, and the issue is rated 8.7 (CVSS v4.0).

Technical details

  • Root cause: AVideo’s enforceRateLimit() function derives the client identity used for throttling from the X-Real-IP and X-Forwarded-For HTTP headers, without validating that the request originated from a trusted proxy.
  • Trigger condition: An attacker sends login requests while rotating the value of these headers, causing each request to appear to originate from a different client.
  • Attack vector: Network, no authentication or user interaction required.
  • Impact: Login rate limiting is rendered ineffective, enabling unlimited/unthrottled password-guessing (brute-force) attempts against user accounts.

Affected software

  • WWBN AVideo, versions 0 through 29.0

Severity

  • CVSS v4.0: 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: 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: Upgrade WWBN AVideo to a version beyond 29.0 that validates trusted proxies before honoring X-Real-IP/X-Forwarded-For headers in the rate-limiting logic.
  • If patching is not immediately possible: terminate/normalize client IP at a trusted reverse proxy or load balancer and strip or override client-supplied X-Real-IP/X-Forwarded-For headers before they reach the application; enforce account lockout or MFA independent of IP-based rate limiting; monitor authentication logs for high-volume login attempts with varying forwarded-IP headers.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge