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

Back
New CVE Detected

CVE-2026-86729 – Unauthenticated Brute-Force Account Takeover – WWBN AVideo (through v29.0)

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86729 is a critical improper authentication-attempt-restriction vulnerability (CWE-307) in WWBN AVideo. An undocumented, unthrottled login endpoint allows unauthenticated attackers to brute-force credentials for any account, including administrators, and leaks authentication status in the response body, enabling reliable account takeover.

Technical details

  • Root cause: the get_api_preauthorize function in plugin/API/API.php performs credential validation but does not apply the rate limiting (10 attempts per 5 minutes) enforced by the documented get_api_signIn login path.
  • Credential oracle: the endpoint returns the same "Invalid credentials" text for both valid and invalid passwords, but the response body’s users_id field discloses the outcome (users_id:1 on success, users_id:0 on failure).
  • Session persistence: a correct password establishes a session cookie that remains valid and usable for subsequent authenticated API requests.
  • Attack vector: network, unauthenticated, no user interaction required; an attacker can send unlimited login attempts with ordinary HTTP requests.
  • Impact: unauthenticated brute-force password guessing leading to full account compromise, including administrative accounts.

Affected software

  • WWBN AVideo, all versions through 29.0 (including the current development commit at time of disclosure)
  • No patched version is available as of publication

Severity

  • CVSS v4.0: 9.1 (Critical) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.4 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: no official patch is currently available; monitor the vendor’s GitHub repository and advisory for a fix and upgrade as soon as one is released.
  • Workarounds: apply rate limiting or account lockout controls to the get_api_preauthorize endpoint (or block/restrict access to it) at the WAF or reverse-proxy layer; enforce IP-based access controls on API endpoints; monitor logs for repeated failed authentication attempts against this endpoint; rotate credentials for accounts that may have been targeted.

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