CVE-2026-40928: AVideo: Missing CSRF Protection on State-Changing JSON Endpoints Enables Forced Comment Creation, Vote Manipulation, and Category Asset Deletion
WWBN AVideo is an open source video platform. In versions 29.0 and prior, multiple AVideo JSON endpoints under objects/ accept state-changing requests via $REQUEST/$GET and persist changes tied to the caller's session user, without any anti-CSRF token, origin check, or referer check. A malicious page visited by a logged-in victim can silently cast/flip the victim's like/dislike on any comment (objects/commentslike.json.php), post a comment authored by the victim on any video, with attacker-chosen text (objects/commentAddNew.json.php), and/or delete assets from any category (objects/categoryDeleteAssets.json.php) when the victim has category management rights. Each endpoint is reachable from a browser via a simple <img src="…"> tag or form submission, so exploitation only requires the victim to load an attacker-controlled HTML resource. Commit 7aaad601bd9cd7b993ba0ee1b1bea6c32ee7b77c contains a fix.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40928?
CVE-2026-40928 is considered a medium severity vulnerability due to its potential for forced actions, like comment creation and vote manipulation.
How do I fix CVE-2026-40928?
To fix CVE-2026-40928, upgrade your AVideo installation to version 30.0 or later, which includes the necessary CSRF protections.
What are the risks associated with CVE-2026-40928?
The risks include unauthorized comment creation, vote manipulation, and category asset deletion, potentially undermining user trust.
Which versions of AVideo are affected by CVE-2026-40928?
AVideo versions 29.0 and prior are affected by CVE-2026-40928.
Is CVE-2026-40928 being actively exploited?
Currently, there is no public information indicating active exploitation of CVE-2026-40928, but system owners should apply the patch to mitigate risks.