Vulnerability in Wizarr (CVE-2026-108264)
Summary
Vulnerability in Wizarr (CVE-2026-108264). Successful exploitation can lead to full system takeover. Exploitable via POST /settings/wizard/import. Mitigation: upgrade to 2026.9.1 or later.
Original description
The description as published by the source.
Wizarr is an advanced user invitation and management system for Jellyfin, Plex, Emby, and other media servers. Prior to 2026.9.1, wizard step Markdown supplied through the editor or imported bundles was evaluated by app/blueprints/wizard/routes.py in the application's non-sandboxed Jinja2 environment with application globals exposed. An authenticated user able to create steps, or an administrator importing an untrusted bundle through POST /settings/wizard/import, could execute arbitrary Python when GET /wizard/{server}/{idx} rendered the stored step; app/jinja_filters.py and app/services/wizard_widgets.py contained additional evaluation sinks. This could execute operating-system commands as the application user, disclose the Flask SECRET_KEY, access connected service credentials and the database, and produce stored cross-site scripting. This issue is fixed in 2026.9.1.
Source: NIST National Vulnerability Database NVD
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-108264 has been found in Wizarr.
Attackers can target a specific entry point like POST /settings/wizard/import over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade Wizarr to 2026.9.1 or later.
If unsure, ask your IT team or search "Wizarr CVE-2026-108264" on the vendor's site.
CVE-2026-108264 (Wizarr) — CWE-1336 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /settings/wizard/import / GET /wizard/{server}/{idx}
Patched: 2026.9.1 — 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-1336) exists in Wizarr. Attackers reach the vulnerable code path via POST /settings/wizard/import.
Check the vendor advisory for the affected versions of Wizarr. Attack surface: POST /settings/wizard/import / GET /wizard/{server}/{idx}.
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to 2026.9.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /settings/wizard/import requests with malformed payloads or SQL meta-characters. Run grep -r 'Wizarr' . 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 'Wizarr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Wizarrを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /settings/wizard/import' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /settings/wizard/importへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Wizarr to 2026.9.1ステージング環境で 2026.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /settings/wizard/import on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。