WWBN AVideo Login Endpoint login.json.php enforceRateLimit User-Agent improper authentication

Summaryinfo

A vulnerability labeled as problematic has been found in WWBN AVideo. This issue affects the function enforceRateLimit of the file login.json.php of the component Login Endpoint. Such manipulation of the argument User-Agent leads to improper authentication. This vulnerability is listed as CVE-2026-82644. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in WWBN AVideo (the affected version unknown) and classified as problematic. Affected by this issue is the function enforceRateLimit of the file login.json.php of the component Login Endpoint. The manipulation of the argument User-Agent with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-82644 since 08/30/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/30/2026).

By approaching the search of inurl:login.json.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• WWBN

Name

• AVideo

License

• open-source

Website

• Product: https://github.com/WWBN/AVideo/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion