WWBN AVideo up to 26.0 Player Skin Configuration Endpoint playerUpdate.json.php ignoreTableSecurityCheck cross-site request forgery

Summaryinfo

A vulnerability categorized as problematic has been discovered in WWBN AVideo up to 26.0. This impacts the function ignoreTableSecurityCheck of the file admin/playerUpdate.json.php of the component Player Skin Configuration Endpoint. The manipulation results in cross-site request forgery. This vulnerability is known as CVE-2026-35181. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in WWBN AVideo up to 26.0. It has been classified as problematic. Affected is the function ignoreTableSecurityCheck of the file admin/playerUpdate.json.php of the component Player Skin Configuration Endpoint. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:

WWBN AVideo is an open source video platform. In versions 26.0 and prior, the player skin configuration endpoint at admin/playerUpdate.json.php does not validate CSRF tokens. The plugins table is explicitly excluded from the ORM's domain-based security check via ignoreTableSecurityCheck(), removing the only other layer of defense. Combined with SameSite=None cookies, a cross-origin POST can modify the video player appearance on the entire platform.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-35181 since 04/01/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

By approaching the search of inurl:admin/playerUpdate.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 best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• WWBN

Name

• AVideo

Version

• 26.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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion