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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 18 Aug 2026, 21:16 UTC Confirmed by NVD
- 31 Oct 2026, 14:01 UTC First seen by agentprime
- 31 Oct 2026, 14:01 UTC Confirmed by OSV