CVE-2026-41057: CWE-346: Origin Validation Error in WWBN AVideo
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.
AI Analysis
Technical Summary
The vulnerability in WWBN AVideo (<= 29.0) stems from incomplete CORS origin validation. Two code paths reflect arbitrary Origin headers with Access-Control-Allow-Credentials set to true: one in plugin/API/router.php lines 4-8, and another via allowOrigin(true) in get.json.php and set.json.php. This misconfiguration allows attackers to perform cross-origin credentialed requests to any API endpoint and read sensitive authenticated responses containing user PII, email, admin status, and session data. The issue is tracked as CWE-346 (Origin Validation Error). A corrective commit (5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13) addresses the problem, but no official patch release or vendor advisory is documented.
Potential Impact
Exploitation of this vulnerability can lead to unauthorized disclosure of sensitive user information including personally identifiable information, email addresses, administrative status, and session-related data. This compromises user privacy and potentially administrative control integrity. The vulnerability does not affect availability and requires user interaction (UI:R) but no privileges (PR:N) and has network attack vector (AV:N).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in commit 5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13; users should monitor WWBN for an official patch release or apply the fix from the commit if feasible. Until patched, restrict cross-origin requests or disable CORS on affected endpoints to prevent exploitation.
CVE-2026-41057: CWE-346: Origin Validation Error in WWBN AVideo
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in WWBN AVideo (<= 29.0) stems from incomplete CORS origin validation. Two code paths reflect arbitrary Origin headers with Access-Control-Allow-Credentials set to true: one in plugin/API/router.php lines 4-8, and another via allowOrigin(true) in get.json.php and set.json.php. This misconfiguration allows attackers to perform cross-origin credentialed requests to any API endpoint and read sensitive authenticated responses containing user PII, email, admin status, and session data. The issue is tracked as CWE-346 (Origin Validation Error). A corrective commit (5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13) addresses the problem, but no official patch release or vendor advisory is documented.
Potential Impact
Exploitation of this vulnerability can lead to unauthorized disclosure of sensitive user information including personally identifiable information, email addresses, administrative status, and session-related data. This compromises user privacy and potentially administrative control integrity. The vulnerability does not affect availability and requires user interaction (UI:R) but no privileges (PR:N) and has network attack vector (AV:N).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability is fixed in commit 5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13; users should monitor WWBN for an official patch release or apply the fix from the commit if feasible. Until patched, restrict cross-origin requests or disable CORS on affected endpoints to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-16T16:43:03.173Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e85dc119fe3cd2cd708093
Added to database: 4/22/2026, 5:33:53 AM
Last enriched: 4/22/2026, 5:34:20 AM
Last updated: 4/23/2026, 1:23:59 AM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.