CVE Catalog

CVE-2026-43877

MediumCVSS 5.4
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.14%

3th percentile - higher than 3% of all known CVEs

Summary

In AVideo up to and including 29.0, objects/userSavePhoto.php accepts a base64 POST parameter and writes decoded bytes to the profile photo, with only User::isLogged() access control. There is no CSRF token, Origin/Referer check, or MIME validation, and the default SameSite=None; Secure cookie policy allows an attacker to overwrite a logged-in user's profile photo and trigger clearCache(true).

Risk Assessment

An attacker can overwrite a victim's profile photo with arbitrary bytes and force costly cache clearing, potentially leading to defacement and disruption.

Recommendation

Update AVideo to a version containing commit 9c38468041505e637101c5943c5370c68f48e3ac or later.

Other vulnerabilities in AVideo

See all
Original NVD description (English source)

WWBN AVideo is an open source video platform. In versions up to and including 29.0, objects/userSavePhoto.php is a legacy profile-photo endpoint that accepts a base64 POST parameter and writes the decoded bytes to videos/userPhoto/photo<users_id>.png. Its only access control is User::isLogged(). It does not end in .json.php, so it is excluded from the project's global autoCSRFGuard (which is suffix-scoped in objects/include_config.php). There is no CSRF token, no Origin/Referer check, and no MIME validation of the decoded bytes. Because AVideo's default cookie policy is SameSite=None; Secure on HTTPS (objects/functionsPHP.php:227), an attacker who lures a logged-in user to a malicious page can overwrite that user's profile photo with arbitrary bytes and also triggers a site-wide clearCache(true) on every forged request. Commit 9c38468041505e637101c5943c5370c68f48e3ac contains an updated fix.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS