Forced comments, votes, and deletion via CSRF
Published Apr 21, 2026 · Updated Apr 21, 2026
Cross-site request forgery in AVideo 29.0 and earlier allows remote attackers to force comments, votes, or asset deletion via a victim's browser. Three state-changing JSON handlers accept GET or request parameters and persist session-bound actions without token, origin, or referer validation. A logged-in victim must load attacker-controlled HTML; ordinary users can be made to post comments or change votes, while category managers can lose category assets.
Summary
What happened
Cross-site request forgery in AVideo 29.0 and earlier allows remote attackers to force comments, votes, or asset deletion via a victim's browser. Three state-changing JSON handlers accept GET or request parameters and persist session-bound actions without token, origin, or referer validation. A logged-in victim must load attacker-controlled HTML; ordinary users can be made to post comments or change votes, while category managers can lose category assets.
The record
- CVE
- CVE-2026-40928
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- World Wide Broadcast Network
- Product
- AVideo
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 29.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory browser-request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo