← Back
CVE-2026-55593
medium
CVSS 6.5
Cross-Site Request Forgery (CSRF) in froxlor/froxlor (CVE-2026-55593)
Summary
vulnerability in froxlor/froxlor (CVE-2026-55593). Data can be tampered with by attackers. Exploitable via ``allowed_from``. Mitigation: upgrade to `2.3.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55593** has been found in froxlor/froxlor.
Attackers can target a specific entry point like ``allowed_from`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade froxlor/froxlor to **2.3.8** or later.
If unsure, ask your IT team or search "froxlor/froxlor CVE-2026-55593" on the vendor's site.
CVE-2026-55593 (froxlor/froxlor) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `allowed_from` / `valid_until` / `admin_customers.php` / `customer_domains.php`
Patched: `2.3.8` — 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
**CSRF** (CWE-352) exists in froxlor/froxlor. Attackers reach the vulnerable code path via ``allowed_from`` without authentication.
📍 Affected scope
froxlor/froxlor — . Attack surface: `allowed_from` / `valid_until` / `admin_customers.php` / `customer_domains.php`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.3.8**.
🛡️ 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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade froxlor/froxlor to 2.3.8ステージング環境で 2.3.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
froxlor/froxlor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.8"}]}]