Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-62988 critical CVSS 9.0

Information Disclosure in froxlor/froxlor (CVE-2026-62988)

Summary

Vulnerability in froxlor/froxlor (CVE-2026-62988). Confidential information can be exposed externally. Exploitable via password. Mitigation: upgrade to 2.3.8 or later.

Original description

The description as published by the source.

Summary

Several Froxlor API command classes return sensitive authentication material in JSON API responses. The affected endpoints retrieve full database rows using SELECT *, SELECT alias.*, or equivalent full-row queries, then return the results directly through $this->response(...) without removing credential-related fields.

The exposed fields include password hashes for customers, administrators, and FTP users, as well as TOTP 2FA seed material for administrator and customer accounts.

This exposes credential-equivalent data to API clients that should not receive it. Password hashes can be cracked offline and reused for account takeover, while exposed TOTP seeds allow generation of valid 2FA codes for affected accounts. When both a password hash and TOTP seed are exposed for the same account, the vulnerability can defeat both authentication factors if the password hash is cracked or the password is otherwise obtained.

Details

The affected API classes retrieve entire database rows and return them without filtering sensitive fields:

lib/Froxlor/Api/Commands/Customers.php

Customers.get() and Customers.listing() select and return customer rows containing sensitive fields, including:

  • password
  • type_2fa
  • data_2fa

When type_2fa = 2, the data_2fa value represents the Base32-encoded TOTP seed used by the customer's authenticator application.

The result is returned through $this->response($result) or `$this->response(['list' => $result]…

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-62988 has been found in froxlor/froxlor.
Attackers can target a specific entry point like password over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.0/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-62988" on the vendor's site.

CVE-2026-62988 (froxlor/froxlor) — CWE-200 / CVSS v3 9.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: password / type_2fa / data_2fa / Customers.get
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

Information disclosure (CWE-200) exists in froxlor/froxlor. Attackers reach the vulnerable code path via password.

📍 Affected scope

Check the vendor advisory for the affected versions of froxlor/froxlor. Attack surface: password / type_2fa / data_2fa / Customers.get.

🔥 Severity

Severity: Critical (CVSS 9.0/10). Confidential information can be exposed externally.

🔧 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