# WWBN AVideo has CORS Origin Reflection with Credentials on Sensitive API Endpoints Enables Cross-Origin Account Takeover

Advisory record · `GHSA-ccq9-r5cw-5hwq`

- **Identifiers:** `GHSA-ccq9-r5cw-5hwq` · `CVE-2026-41056` · `PKSA-5c4b-gnfd-8xsq`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-942](https://cwe.mitre.org/data/definitions/942.html)
- **Tags:** [CWE-942](https://agentprime.io/advisories/tag/cwe-942.md)
- **Published:** 14 Apr 2026
- **Updated:** 5 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Apr 2026, 23:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wwbn/avideo` (Packagist): affected `<=29.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GHSA-ccq9-r5cw-5hwq: The WWBN AVideo package (wwbn/avideo, Packagist) through version 29.0 reflects any arbitrary Origin header with Access-Control-Allow-Credentials set to true on its primary API endpoints. A attacker who gets a logged-in user to visit a malicious web page can read authenticated API responses, including personal data, livestream credentials and stream keys, and can send state-changing requests as that user. No fixed version is listed. The source gives no workaround.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ccq9-r5cw-5hwq)

## Sources

- [GitHub Advisory Database: GHSA-ccq9-r5cw-5hwq](https://github.com/advisories/GHSA-ccq9-r5cw-5hwq)
- [OSV: GHSA-ccq9-r5cw-5hwq](https://osv.dev/vulnerability/GHSA-ccq9-r5cw-5hwq)
- <https://github.com/WWBN/AVideo/security/advisories/GHSA-ccq9-r5cw-5hwq>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41056>
- <https://github.com/WWBN/AVideo/commit/caf705f38eae0ccfac4c3af1587781355d24495e>
- <https://github.com/WWBN/AVideo>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ccq9-r5cw-5hwq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ccq9-r5cw-5hwq/>. Everything for agents: <https://agentprime.io/llms.txt>.