# CVE-2026-29093: WWBN AVideo: Unauthenticated PHP session store exposed to host network via published memcached port

> Unauthenticated memcached exposure allows attackers to hijack sessions, impersonate admins, or destroy sessions in WWBN AVideo.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-xxpw-32hf-q8v9

## What is CVE-2026-29093?

CVE-2026-29093 is a high-severity vulnerability in Wwbn Avideo, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 24.0, the official docker-compose.yml publishes the memcached service on host port 11211 (0.0.0.0:11211) with no authentication, while the Dockerfile configures PHP to store all user sessions in that memcached instance. An attacker who can reach port 11211 can read, modify, or flush session data — enabling session hijacking, admin impersonation, and mass session destruction without any application-level authentication. This issue has been patched in version 24.0.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-29093?

2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 21.0 | None |
| `wwbn/avideo` | Packagist | All versions to 21.0 | None |

Products: Wwbn Avideo.

## How do I fix CVE-2026-29093?

No fix has been published for CVE-2026-29093 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29093 being exploited?

There is no known exploitation of CVE-2026-29093 in the wild and no public exploit code.

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29093 and fix it if it is affected.

What it is: CVE-2026-29093 is a high-severity vulnerability in Wwbn Avideo, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29093 in the wild and no public exploit code.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 21.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 21.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29093/ (Markdown: https://insights.sbomify.com/CVE-2026-29093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29093
- OSV: https://osv.dev/vulnerability/CVE-2026-29093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29093/
Summaries are generated and may contain mistakes; the official description above is the record.