WWBN AVideo up to 29.7.0 AI receiveAsync.json.php lang path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in WWBN AVideo up to 29.7.0. Impacted is an unknown function of the file plugin/AI/receiveAsync.json.php of the component AI. The manipulation of the argument lang leads to path traversal. This vulnerability is listed as CVE-2026-124424. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in WWBN AVideo up to 29.7.0 and classified as problematic. This issue affects some unknown functionality of the file plugin/AI/receiveAsync.json.php of the component AI. The manipulation of the argument lang with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. The summary by CVE is:

WWBN AVideo contains a path traversal vulnerability in plugin/AI/receiveAsync.json.php that allows holders of any valid AI token to write arbitrary .vtt files by injecting traversal sequences into the unsanitized response[lang] parameter. Attackers can send a type=translation request with a crafted lang value to plant attacker-controlled content in the webroot or overwrite other users' subtitle files.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-124424 since 11/08/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/08/2026). MITRE ATT&CK project uses the attack technique T1006 for this issue.

By approaching the search of inurl:plugin/AI/receiveAsync.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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• WWBN

Name

• AVideo

Version

• 29.0
• 29.1
• 29.2
• 29.3
• 29.4
• 29.5
• 29.6
• 29.7.0

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion