WWBN AVideo Cross-Origin Request Vulnerability (CVE-2026-41056)
WWBN AVideo versions 29.0 and below are vulnerable to cross-origin request attacks (CVE-2026-41056) due to improper handling of Origin headers and session cookies, allowing unauthorized access to user data and system modifications.
WWBN AVideo, an open-source video platform, is vulnerable to a cross-origin request vulnerability (CVE-2026-41056) in versions 29.0 and below. The vulnerability stems from the allowOrigin($allowAll=true) function located in objects/functions.php, which improperly reflects arbitrary Origin headers in the Access-Control-Allow-Origin response header and also sets Access-Control-Allow-Credentials: true. This function is called by the plugin/API/get.json.php and plugin/API/set.json.php API endpoints. The combination of this behavior with the application's use of SameSite=None session cookies allows attackers to make credentialed cross-origin requests. This can lead to the theft of sensitive user information (PII), access to livestream keys, and the ability to perform unauthorized actions on behalf of legitimate users. The vulnerability was patched in commit caf705f38eae0ccfac4c3af1587781355d24495e.
Attack Chain
- Attacker crafts a malicious website with JavaScript code designed to make cross-origin requests to a vulnerable AVideo instance.
- Victim visits the attacker's malicious website in a browser where they are also authenticated to the AVideo application due to the
SameSite=Nonecookie policy. - The malicious JavaScript initiates an HTTP request to
plugin/API/get.json.phporplugin/API/set.json.phpon the AVideo server, including the victim's session cookie. - The AVideo server, due to the vulnerable
allowOriginfunction, reflects the attacker's origin in theAccess-Control-Allow-Originheader and setsAccess-Control-Allow-Credentials: true. - The victim's browser, trusting the response due to the permissive CORS policy, allows the JavaScript code to read the response from the AVideo server.
- The attacker's JavaScript extracts sensitive information from the API response, such as user PII or livestream keys.
- The attacker exfiltrates the stolen information to a server under their control.
- The attacker leverages stolen credentials or keys to access user accounts, modify content, or conduct unauthorized live streams.
Impact
Successful exploitation of CVE-2026-41056 can result in the compromise of user accounts, theft of sensitive personal information, and unauthorized access to livestreaming functionality within AVideo. There is no specific victim count available, but all installations of AVideo version 29.0 and below are vulnerable. The impact could range from defacement of video content to full account takeover and potential financial losses due to unauthorized livestreaming.
Recommendation
- Immediately upgrade all AVideo instances to a version containing the fix from commit caf705f38eae0ccfac4c3af1587781355d24495e.
- Monitor web server logs for suspicious
Originheaders targeting the/plugin/API/get.json.phpand/plugin/API/set.json.phpendpoints using the Sigma rules provided. - Implement a Web Application Firewall (WAF) rule to reject requests with unusual or unexpected
Originheaders to mitigate potential exploitation attempts of CVE-2026-41056. - Review and harden the AVideo application's session management and CORS policies to prevent future cross-origin vulnerabilities.
Detection coverage 2
Detect Suspicious Origin Header to AVideo API Endpoints
mediumDetects potentially malicious requests to AVideo API endpoints with unusual Origin headers, indicating a possible CORS vulnerability exploitation attempt.
AVideo API Endpoint Access with Credentials
lowDetects access to AVideo API endpoints where credentials are being passed in the request. This can be useful for detecting possible exploitation of CVE-2026-41056.
Detection queries are available on the platform. Get full rules →