How to Fix CVE-2026-40928: Cross-site request forgery in AVideo
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 5.4 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | WWBN AVideo <= 29.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-352: CWE-352: Cross-Site Request Forgery (CSRF) |
What is CVE-2026-40928?
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/comments_like.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.
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s avideo 2>/dev/null | grep -i version
rpm -q avideo 2>/dev/null
avideo --version 2>/dev/null
Compare what you see against the Affected row above (WWBN AVideo <= 29.0). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-40928
The primary fix is to upgrade AVideo to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: See vendor advisory.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade avideo
avideo --version 2>/dev/null || dpkg -s avideo | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security avideo -y
rpm -q avideo
SUSE / openSUSE
sudo zypper patch --category security
rpm -q avideo
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-40928 affecting AVideo
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-40928-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detecting installed version of AVideo"
$pkg = winget list --id "AVideo" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\AVideo-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\AVideo" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to latest"
winget upgrade --id "AVideo" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "AVideo"
Write-Host "Fix applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-40928 affecting AVideo
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-40928-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s avideo 2>/dev/null | grep -i version || echo "avideo not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q avideo || echo "avideo not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-40928-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/avideo /etc/avideo.d /etc/avideo.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: latest)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y avideo
elif command -v dnf >/dev/null; then
dnf upgrade --security -y avideo
elif command -v yum >/dev/null; then
yum update -y avideo
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s avideo 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q avideo
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop avideo
sudo systemctl disable avideo
How to verify the fix worked
# Linux
avideo --version 2>/dev/null || dpkg -s avideo | grep -i version
rpm -q avideo 2>/dev/null || true
# Windows
winget list | findstr /I "avideo"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above the patched build documented in the advisory. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-42261: Improper Input Validation in PromptHub — Improper Input Validation in PromptHub
- How to Fix CVE-2026-27691: Integer overflow in iccDEV — Integer overflow in iccDEV
- How to Fix CVE-2026-33482: Command Injection in AVideo , Command Injection in AVideo
- How to Fix CVE-2026-5618: kalcaddle kodbox shareMake/shareCheck server-side request forgery , kalcaddle kodbox shareMake/shareCheck server-side request forgery
- How to Fix CVE-2026-33933: Critical Vulnerability in openemr , Critical Vulnerability in openemr
Is CVE-2026-40928 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
5.4 (medium). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://github.com/WWBN/AVideo/security/advisories/GHSA-x2pw-9c38-cp2j
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40928
- https://github.com/WWBN/AVideo/commit/7aaad601bd9cd7b993ba0ee1b1bea6c32ee7b77c
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*