Cyber Resilience

CVE-2026-41057

Wwbn Avideo ≤ 29.0

Public PoC
Published
21 April 2026
Modified
24 April 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
EPSS Score 0.0013 3th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2026-41057 is a high-severity Origin Validation Error (CWE-346) vulnerability in Wwbn Avideo. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique DHCP Spoofing (T1557.003); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

WWBN AVideo, an open source video platform, is affected by CVE-2026-41057 in versions 29.0 and below. The vulnerability stems from an incomplete CORS origin validation fix introduced in commit 986e64aad. Specifically, two code paths still reflect arbitrary Origin headers while allowing credentials for all /api/* endpoints: (1) plugin/API/router.php lines 4-8 unconditionally reflect any origin before application code executes, and (2) the allowOrigin(true) function invoked by get.json.php and set.json.php reflects any origin with Access-Control-Allow-Credentials: true. This flaw is classified under CWE-346 (Origin Validation Error) with a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N).

An attacker can exploit this vulnerability by tricking a victim into visiting a malicious website, enabling cross-origin credentialed requests to the vulnerable AVideo instance's API endpoints. No privileges are required (PR:N), and exploitation is network-accessible (AV:N) with low complexity (AC:L), though it requires user interaction (UI:R), such as clicking a link. Successful exploitation allows the attacker to read authenticated responses, disclosing sensitive user data including PII, email addresses, admin status, and session-sensitive information, with high confidentiality impact (C:H) and low integrity impact (I:L).

The GitHub security advisory GHSA-ff5q-cc22-fgp4 and fixing commit 5e2b897ccac61eb6daca2dee4a6be3c4c2d93e13 detail the patch, which addresses the incomplete CORS validation by properly restricting origin reflection and credential allowance in the affected code paths. Security practitioners should upgrade to a version incorporating this commit and verify CORS headers on API endpoints.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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)…

more

`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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557.003 DHCP Spoofing Credential Access
Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1557.001 Name Resolution Poisoning and SMB Relay Credential Access
By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system.
T1557.002 ARP Cache Poisoning Credential Access
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices.
T1557.004 Evil Twin Credential Access
Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as [Network Sniffing](https://attack.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33690Same product: Wwbn Avideo
CVE-2026-33716Same product: Wwbn Avideo
CVE-2026-39370Same product: Wwbn Avideo
CVE-2026-33485Same product: Wwbn Avideo
CVE-2026-33039Same product: Wwbn Avideo
CVE-2026-41055Same product: Wwbn Avideo
CVE-2025-34436Same product: Wwbn Avideo
CVE-2026-33502Same product: Wwbn Avideo
CVE-2026-33237Same product: Wwbn Avideo
CVE-2026-33297Same product: Wwbn Avideo

Affected Assets

wwbn
avideo
≤ 29.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement directly requires validating the source of data before allowing transmission or receipt.

Device identification and authentication mandates verifying the source before establishing connections.

Session authenticity mechanisms require validation that communications originate from the expected party.

Boundary protection at interfaces enforces checks on the origin of incoming communications.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Authentication directly verifies the source of users/services/hardware, mitigating origin validation failures.

PR.AA-04 mostly match
prevents

Verifying identity assertions enforces origin validation for conveyed claims.

ID.AM-03 partial match
prevents

Documenting authorized flows supports origin validation by defining expected sources.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access requires origin checks on communication sources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

Network security controls enforce origin validation at network boundaries.

mitigates

Security of network services includes validating the authenticity of service endpoints.

mitigates

Network segregation reduces exposure but does not directly validate origins.

prevents

Application security requirements explicitly call for origin validation of inputs and communications.

prevents

Secure architecture principles encourage origin checks but do not mandate them.

prevents

Secure coding practices include implementing proper origin validation to prevent spoofing.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-346
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-346
  • V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-346

References