Authorization Flaw in froxlor/froxlor (CVE-2026-41235)
Summary
Vulnerability in froxlor/froxlor (CVE-2026-41235). Successful exploitation can lead to full system takeover. Exploitable via POST /customer_ftp.php. Mitigation: upgrade to 2.3.7 or later.
Original description
The description as published by the source.
Froxlor is open source server administration software. Version 2.3.6 lets administrators configure system.available_shells as the approved shell list that customers may assign to FTP users. However, the server-side FTP account handlers do not enforce that whitelist when processing add or edit requests. As a result, an authenticated customer with shell delegation enabled can submit an arbitrary shell such as /bin/bash even when the panel UI only offers more restricted choices. In deployments that use the default nssextrausers integration, the attacker-controlled shell is then propagated into the system account database, leading to real host shell access. Version 2.3.7 fixes the issue.
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-41235 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.
What to do: upgrade froxlor/froxlor to 2.3.7 or later.
If unsure, ask your IT team or search "froxlor/froxlor CVE-2026-41235" on the vendor's site.
CVE-2026-41235 (froxlor/froxlor) — CWE-863
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /customer_ftp.php / system.available_shells / nssextrausers / ftp_users.shell
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.
Incorrect authorization (CWE-863) exists in froxlor/froxlor. Attackers reach the vulnerable code path via POST /customer_ftp.php.
Check the vendor advisory for the affected versions of froxlor/froxlor. Attack surface: POST /customer_ftp.php / system.available_shells / nssextrausers / ftp_users.shell.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.3.7.
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 /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
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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt 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 があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade froxlor/froxlor to 2.3.7ステージング環境で 2.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /customer_ftp.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com