Vulnerability in wwbn/avideo (CVE-2026-33692)
Summary
Vulnerability in wwbn/avideo (CVE-2026-33692). Confidential information can be exposed externally. Exploitable via GET /.env. Mitigation: upgrade to 29.0 or later.
Original description
The description as published by the source.
WWBN AVideo is an open source video platform. Versions prior to 29.0 expose .env files to unauthenticated users through the official Docker compose configuration. The official docker-compose.yml mounts the entire project root directory as the Apache document root, causing the .env file — which contains database credentials, admin passwords, and infrastructure configuration — to be served as a static file at /.env. No .htaccess rule or Apache configuration blocks access to dotfiles. Exploitation enables direct database access, admin panel takeover, and further lateral movement within the Docker network. This issue has been resolved in version 29.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33692 has been found in wwbn/avideo.
Attackers can target a specific entry point like GET /.env over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade wwbn/avideo to 29.0 or later.
If unsure, ask your IT team or search "wwbn/avideo CVE-2026-33692" on the vendor's site.
CVE-2026-33692 (wwbn/avideo) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /.env / DB_MYSQL_USER / DB_MYSQL_PASSWORD / SYSTEM_ADMIN_PASSWORD
Patched: 29.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in wwbn/avideo. Attackers reach the vulnerable code path via GET /.env without authentication.
Check the vendor advisory for the affected versions of wwbn/avideo. Attack surface: GET /.env / DB_MYSQL_USER / DB_MYSQL_PASSWORD / SYSTEM_ADMIN_PASSWORD.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 29.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /.env requests with malformed payloads or SQL meta-characters. Run grep -r 'wwbn/avideo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wwbn/avideo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wwbn/avideoを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /.env' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /.envへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade wwbn/avideo to 29.0ステージング環境で 29.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /.env on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com