By Null Ventures MCP platform
Menu

vulnerability / NVI-00005929 / Revision 5

Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints

GitHub lists this reviewed advisory for froxlor/froxlor. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-7788-ghfq-c6mhCVE-2026-62988

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

CVSS

9 critical

GitHub source severity; exploitability and local consequence require separate evidence.

As of · GitHub Advisory Database

EPSS

0.627%

FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.50187. Missing scores are unknown.

As of · FIRST EPSS

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

froxlor/froxlor

source listed
  • < 2.3.8

## 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

GitHub Advisory Database

froxlor/froxlor

source listed
  • ECOSYSTEM: introduced 0; fixed 2.3.8

## 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

GitHub Advisory Database via OSV

03 / Response

What to do next

  1. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS

  2. vendor patch

    The original advisory lists fixed boundaries 2.3.8 for froxlor/froxlor. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-7788-ghfq-c6mh ↗

    GitHub Advisory Database · vendor advisory

    Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.

  2. GHSA-7788-ghfq-c6mh ↗

    GitHub Advisory Database via OSV · vendor advisory

    Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.

  3. CVE-2026-62988 ↗

    FIRST EPSS · official catalog

    Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 5 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  2. Revision 4 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  3. Revision 3 ·

    Source facts changed; compare the preserved prior revision.

  4. Revision 2 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

  5. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗