Advisory record · GHSA-f9rx-7wf7-jr36

Froxlor's API Authentication bypasses 2FA Authentication

CVSS 8.1 HighEPSS 0.0032 · 25th percentile

Published by the GitHub Advisory Database at 3 Jun 2026, 21:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
froxlor/froxlorPackagist<2.3.72.3.7
Identifiers
GHSA-f9rx-7wf7-jr36 · CVE-2026-52793 · PKSA-bhjh-v6gp-f43f
Weakness (CWE)
CWE-287
Published
3 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Froxlor versions before 2.3.7 do not enforce two-factor authentication on API requests, so an API key and secret alone grant access to the API even on accounts where 2FA is enabled for the web UI. An attacker who obtains a leaked API key and secret for such an account could use the API's operations without a second factor. The fix is to upgrade Froxlor to version 2.3.7 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 18 Aug 2026, 21:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:01 UTC First seen by agentprime
  3. 31 Oct 2026, 14:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.