← Back
CVE-2026-41236
high
CVSS 8.8
Vulnerability in froxlor/froxlor (CVE-2026-41236)
Summary
vulnerability in froxlor/froxlor (CVE-2026-41236). Successful exploitation can lead to full system takeover. Exploitable via `POST /customer_ftp.php`. Mitigation: upgrade to `2.3.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41236** has been found in froxlor/froxlor.
Attackers can target a specific entry point like `POST /customer_ftp.php` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade froxlor/froxlor to **2.3.7** or later.
If unsure, ask your IT team or search "froxlor/froxlor CVE-2026-41236" on the vendor's site.
CVE-2026-41236 (froxlor/froxlor) — CWE-59 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /customer_ftp.php / `REBUILD_NSSUSERS` / `authorized_keys` / `root`
Patched: `2.3.7` — 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.
❓ What is the problem
**A vulnerability** (CWE-59) exists in froxlor/froxlor. Attackers reach the vulnerable code path via `POST /customer_ftp.php` without authentication.
📍 Affected scope
froxlor/froxlor — . Attack surface: POST /customer_ftp.php / `REBUILD_NSSUSERS` / `authorized_keys` / `root`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.3.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /customer_ftp.php` requests with malformed payloads or SQL meta-characters. Run `grep -r 'froxlor/froxlor' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'froxlor/froxlor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `froxlor/froxlor` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /customer_ftp.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /customer_ftp.php` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade froxlor/froxlor to 2.3.7ステージング環境で 2.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /customer_ftp.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
froxlor/froxlor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.7"}]}]
Packagist
froxlor/froxlor
[{"type":"ECOSYSTEM","events":[{"introduced":"2.3.6"},{"fixed":"2.3.7"}]}]