/

CVE-2026-86729

Severity:

HIGH RISK

(7.4)

Unrestricted Login Attempts (CWE-307) in AVideo API

CVE-2026-86729

Deferred

Vulnerability type

Category:

Improper Restriction of Authentication Attempts

CWE:

CWE-307

Impact:

Unauthenticated Account Takeover

Severity:

HIGH RISK

(7.4)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

WWBN AVideo exposes an undocumented preauthorization API path that checks credentials without applying the rate limit used by the standard sign-in endpoint. An unauthenticated attacker may use unlimited remote password guesses against arbitrary accounts, while response data can reveal whether authentication succeeded and establish a usable session.

Affected context

The issue occurs in AVideo deployments where the API plugin exposes the get_api_preauthorize handler and permits unauthenticated clients to submit login attempts. Risk increases when this alternate authentication path lacks the throttling, lockout, monitoring, and response protections applied to the primary sign-in flow, particularly for privileged accounts.

Exploit preconditions

  • Attack surface: Publicly reachable AVideo API endpoint
  • Required access: No prior authentication is generally required
  • Trigger point: Credential processing through the preauthorization handler
  • Why exploitation is possible: The alternate login path does not enforce

equivalent attempt throttling, allowing repeated guesses against selected

accounts

  • Additional exposure: Response fields distinguish successful and failed

authentication and a successful check can create an authenticated session

Why this happens

The vulnerability results from an undocumented authentication path that performs credential verification without inheriting the rate-limiting and abuse controls of the primary sign-in endpoint. This is a failure to sufficiently restrict repeated authentication attempts, mapping to CWE-307. The response also exposes authentication-state information through identity-related fields, and the resulting session remains usable for authenticated API operations.

Potential impact

  • An attacker may guess passwords for arbitrary user accounts
  • Privileged accounts could be taken over if their credentials are recovered
  • Attackers could obtain authenticated sessions for compromised users
  • Account data and protected API functionality could be accessed or modified
  • Repeated attempts could increase operational and monitoring burden

General mitigation guidance

Mitigation generally focuses on consolidating authentication through a single

consistently protected path and reducing the value of automated guessing.

Common defensive patterns include:

  • Applying rate limits, progressive delays, and account or identity-based

protections to every credential-verification endpoint

  • Removing undocumented or redundant authentication paths when they are not

required

  • Returning uniform authentication responses that do not disclose identity or

success-state details through auxiliary fields

  • Requiring strong authentication controls, including multifactor

authentication for privileged accounts

  • Limiting session privileges and scope according to the authenticated user's

role

  • Centralizing authentication policy enforcement so alternate handlers cannot

bypass it

  • Monitoring failed attempts, distributed guessing patterns, and unusual

session creation activity

How teams detect issues like this

Detection approaches may include:

  • Static analysis and code review searches for authentication handlers that

verify credentials without shared rate-limit or lockout controls

  • Inventorying API routes for undocumented, duplicate, or alternate login

paths

  • Reviewing response schemas for user identifiers or fields that distinguish

authentication outcomes

  • Integration tests that verify equivalent throttling and response behavior

across all authentication endpoints

  • Web application firewall and API gateway policies that detect high-volume

credential attempts across accounts or source addresses

  • Logging and alerting on repeated failures, distributed password guessing,

and unexpected authenticated-session creation

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-vvqm-mgc5-hhx3
vulncheck.comvulncheck.com/advisories/wwbn-avideo-unrestricted-authentication-attempts-via-get-api-preauthorize

Frequently asked

questions

Yes. The affected API path may be reachable over the network, and prior

authentication is generally not required. Exploitability depends on whether

the endpoint is exposed and whether surrounding access controls restrict it.

An attacker typically needs network access to the AVideo API and a target

account identifier. No valid credentials are required to begin repeated

authentication attempts.

Route all credential checks through a uniformly protected authentication

service, enforce rate limiting and abuse controls at every entry point, and

avoid response fields that reveal authentication state or user identity.

Maintain an inventory of authentication routes, test alternate handlers for

equivalent security controls, require multifactor authentication for

privileged users, and monitor distributed password-guessing activity.

Find out what's already
exploitable in your codebase.