CVE-2026-41057: AVideo has CORS Origin Reflection Bypass via plugin/API/router.php and allowOrigin(true) that Exposes Authenticated API Responses
WWBN AVideo is an open source video platform. In versions 29.0 and below, the CORS origin validation fix in commit 986e64aad is incomplete. Two separate code paths still reflect arbitrary Origin headers with credentials allowed for all /api/ endpoints: (1) plugin/API/router.php lines 4-8 unconditionally reflect any origin before application code runs, and (2) allowOrigin(true) called by get.json.php and set.json.php reflects any origin with Access-Control-Allow-Credentials: true. An attacker can make cross-origin credentialed requests to any API endpoint and read authenticated responses containing user PII, email, admin status, and session-sensitive data. Commit 5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13 contains a fix.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41057?
CVE-2026-41057 has been classified as a critical vulnerability due to its potential to expose authenticated API responses.
How do I fix CVE-2026-41057?
To fix CVE-2026-41057, upgrade AVideo to version 29.1 or later, which addresses the CORS origin validation issue.
What does CVE-2026-41057 affect?
CVE-2026-41057 affects WWBN AVideo versions 29.0 and below, specifically related to CORS configuration.
What are the risks associated with CVE-2026-41057?
The risks include unauthorized access to sensitive user data through exposed authenticated API responses.
Is CVE-2026-41057 a common vulnerability?
CVE-2026-41057 is notable within the community due to its impact on a widely used open-source video platform.