Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54348 high CVSS 7.2

SQL Injection in froxlor/froxlor (CVE-2026-54348)

Summary

SQL injection in froxlor/froxlor (CVE-2026-54348). Successful exploitation can lead to full system takeover. Exploitable via panel_admins.ip. Mitigation: upgrade to 2.3.8 or later.

Original description

The description as published by the source.

Summary

A second-order SQL injection vulnerability in Froxlor's admin API allows an authenticated administrator to store a crafted SQL payload in the panel_admins.ip column via the Admins.add or Admins.update endpoint. The payload executes as a UNION-based SQL injection the next time IpsAndPorts.listing is called by the poisoned account, returning arbitrary data from the database — including all administrator login names and bcrypt password hashes.

Details

The vulnerability spans two code locations that form a store-then-trigger chain.

Stage 1 — Unsanitized array stored as JSON — lib/Froxlor/Api/Commands/Admins.php:251,358

$ipaddress = $this->getParam('ipaddress', true, -1);
// No type enforcement or content validation on $ipaddress.
// PHP evaluates (is_array([...]) && non_empty_array > 0) as true,
// so any attacker-controlled array is JSON-encoded and stored verbatim.
'ip' => empty($ipaddress) ? "" : (is_array($ipaddress) && $ipaddress > 0
    ? json_encode($ipaddress)   // ← attacker payload written to panel_admins.ip
    : -1),

The INSERT/UPDATE uses a prepared statement, so the write itself is safe. The danger is what is stored.

Stage 2 — JSON payload imploded directly into SQL — lib/Froxlor/Api/Commands/IpsAndPorts.php:71-77

if (!empty($this->getUserDetail('ip')) && $this->getUserDetail('ip') != -1) {
    // json_decode restores the array; implode joins elements with no casting or escaping
    $ip_where = "WHER…

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-54348 has been found in froxlor/froxlor.
Attackers can target a specific entry point like panel_admins.ip over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/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-54348" on the vendor's site.

CVE-2026-54348 (froxlor/froxlor) — CWE-89 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: panel_admins.ip / Admins.add / Admins.update / IpsAndPorts.listing
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

SQL injection (CWE-89) exists in froxlor/froxlor. Attackers reach the vulnerable code path via panel_admins.ip.

📍 Affected scope

Check the vendor advisory for the affected versions of froxlor/froxlor. Attack surface: panel_admins.ip / Admins.add / Admins.update / IpsAndPorts.listing.

🔥 Severity

Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.

🔧 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'froxlor/froxlor' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で froxlor/froxlor を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade froxlor/froxlor to 2.3.8

    ステージング環境で 2.3.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer froxlor/froxlor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.8"}]}]
Packagist froxlor/froxlor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details