WWBN AVideo up to 29.7.1 Live plugin verifyTokenForAction.json.php live_transmitions_history_id improper authorization

Summaryinfo

A vulnerability has been found in WWBN AVideo up to 29.7.1 and classified as critical. Affected by this issue is some unknown functionality of the file verifyTokenForAction.json.php of the component Live plugin. The manipulation of the argument live_transmitions_history_id leads to improper authorization. This vulnerability is uniquely identified as CVE-2026-126541. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in WWBN AVideo up to 29.7.1. This issue affects an unknown part of the file verifyTokenForAction.json.php of the component Live plugin. The manipulation of the argument live_transmitions_history_id with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

WWBN AVideo through 29.7.1 contains a missing authorization vulnerability in Live plugin restream endpoints that allows authenticated streamers to obtain other users' stream keys by supplying arbitrary live_transmitions_history_id values. Attackers can redeem the issued action tokens at verifyTokenForAction.json.php to retrieve victims' HLS URLs and stream keys, then publish as the victim or restream private or pay-per-view lives.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-126541 since 11/11/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/11/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion