Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-33692 – Unauthenticated .env File Exposure – WWBN AVideo prior to 29.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-33692 is a high-severity sensitive file exposure vulnerability affecting WWBN AVideo, an open-source video streaming platform, in all versions prior to 29.0. The official Docker Compose configuration mounts the entire project root directory as the Apache document root, causing the .env file — which contains database credentials, admin passwords, and internal network topology — to be served unauthenticated as a plain static file at /.env. The issue has been resolved in version 29.0.

Technical details

  • Root cause: The official docker-compose.yml bind-mounts the entire AVideo project root as the Apache document root. No .htaccess rule or Apache virtual host directive restricts access to dotfiles, leaving .env directly reachable over HTTP.
  • Trigger conditions: Any AVideo instance deployed using the official Docker Compose method and exposed to the internet is affected. No special preconditions, credentials, or user interaction are required.
  • Attack vector: An unauthenticated remote attacker sends a single HTTP GET request to /.env on the target host. The Apache web server returns the full contents of the environment file as a plain-text response.
  • Exposed data: The .env file contains database hostname and credentials (DB_MYSQL_USER, DB_MYSQL_PASSWORD), the system administrator password (SYSTEM_ADMIN_PASSWORD), TLS certificate file paths, and the internal Docker network subnet (NETWORK_SUBNET).
  • Impact: Successful exploitation yields direct database access, full administrative panel takeover, and the information required for lateral movement within the Docker network. Confidentiality impact is rated High; no integrity or availability impact is introduced by the exposure itself.

Affected software

  • WWBN AVideo — all versions prior to 29.0 deployed via the official Docker Compose configuration

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate (patch): Upgrade to AVideo version 29.0, which resolves the misconfiguration.
  • Interim workaround (if immediate patching is not possible): Add an Apache .htaccess rule to block access to all dotfiles: 
    <FilesMatch "^.">
    Order Allow,Deny
    Deny from all
</FilesMatch>

    Alternatively, configure the Apache virtual host to explicitly deny access to dotfiles, and ensure the .env file is not located within any directory served by Apache.

  • Review all running Docker-based AVideo deployments to confirm whether .env is publicly accessible, and rotate any credentials contained in exposed files immediately.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge