WWBN AVideo up to 29.7.1 aVideoEncoderStatus.json.php useVideoHashOrLogin improper authorization

Summaryinfo

A vulnerability classified as problematic was found in WWBN AVideo up to 29.7.1. This vulnerability affects the function useVideoHashOrLogin of the file aVideoEncoderStatus.json.php. Executing a manipulation can lead to improper authorization. This vulnerability appears as CVE-2026-126805. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic was found in WWBN AVideo up to 29.7.1. This vulnerability affects the function useVideoHashOrLogin of the file aVideoEncoderStatus.json.php. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

WWBN AVideo through 29.7.1 contains an incorrect authorization vulnerability that allows delegated Videos Admin users to obtain video_id_hash values bound to any video owner via encoder endpoints like aVideoEncoderStatus.json.php. Attackers can request the hash for an administrator-owned video and replay it through useVideoHashOrLogin() for password-less login, gaining plugin upload, configuration, and user management access.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-126805 since 11/11/2026. The exploitation appears to be easy. The attack can be initiated remotely. Additional levels of successful authentication are necessary 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 11/11/2026). The MITRE ATT&CK project declares the attack technique as T1548.002.

By approaching the search of inurl:aVideoEncoderStatus.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

Version

• 29.7.0
• 29.7.1

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