dbcve.org
AvideoApplication · Wwbn

CVE-2026-29093

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In WWBN AVideo versions before 24.0, the docker-compose.yml exposes the memcached service on host port 11211 to all network interfaces (0.0.0.0:11211) without authentication, while the PHP application stores all user sessions in this memcached instance. Attackers 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 credentials.

MitigationUpgrade to version 24.0 or later. Alternatively, bind memcached to localhost only (127.0.0.1:11211) in docker-compose.yml or enable memcached authentication to prevent unauthenticated network access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvideoApplication
Affected:< 24.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AVideo version
    Check the version.php file in the AVideo installation directory, or look at the version number displayed in the admin dashboard under 'Update' or 'About' section.
    Affected if The installed version is below 24.0 (e.g., 23.x, 22.x, etc.)
  2. Verify memcached is running and exposed
    Run 'netstat -tlnp | grep 11211' or 'ss -tlnp | grep 11211' to see which address memcached is listening on.
    Affected if Memcached is bound to 0.0.0.0:11211 (all interfaces) rather than 127.0.0.1:11211 (localhost only)
  3. Check if memcached allows unauthenticated access
    Attempt to connect to memcached using 'telnet localhost 11211' or 'nc -v localhost 11211' and run 'stats' or 'version' commands without providing credentials.
    Affected if The connection succeeds and returns server statistics without requiring any authentication
  4. Confirm PHP uses memcached for sessions
    Check the PHP configuration file (php.ini) for 'session.save_handler = memcached' and 'session.save_path' pointing to the vulnerable memcached instance.
    Affected if PHP is configured to store sessions in memcached and the save_path references the exposed memcached server

A user is affected if running AVideo version below 24.0 with memcached bound to 0.0.0.0:11211 and PHP configured to store sessions there without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.0 or later
Fixed in 24.0
Interim mitigation

Upgrade to version 24.0 or later. Alternatively, bind memcached to localhost only (127.0.0.1:11211) in docker-compose.yml or enable memcached authentication to prevent unauthenticated network access.

Recommended fix High confidence

version 24.0

  1. Back up your current Avideo data and configuration
  2. Upgrade Avideo to version 24.0 or later
  3. After upgrading, verify that memcached is no longer exposed on 0.0.0.0:11211 without authentication by reviewing the docker-compose.yml
  4. Confirm that session functionality works correctly after the upgrade
  5. If you require memcached externally, configure authentication and bind to localhost only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data