---
id: CVE-2026-52793
title: Froxlor is open source server administration software
summary: >-
  Froxlor is open source server administration software. Prior to 2.3.7, the API
  authentication path in lib/Froxlor/Api/FroxlorRPC.php and
  FroxlorRPC::validateAuth accepts an API key and secret for an administrator or
  customer account with…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'
cwe:
  - CWE-287
published: '2026-08-18'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T21:02:26.047'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-52793'
references:
  - url: >-
      https://github.com/froxlor/froxlor/commit/7fc21dc6f8d22673e4ddc765b710c9d3f85cb001
    label: security-advisories@github.com
  - url: 'https://github.com/froxlor/froxlor/releases/tag/2.3.7'
    label: security-advisories@github.com
  - url: 'https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36'
    label: security-advisories@github.com
  - url: 'https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00325
epssPercentile: 0.22873
ingestedAt: '2026-09-08T21:11:12.283Z'
---

## Overview

Froxlor is open source server administration software. Prior to 2.3.7, the API authentication path in lib/Froxlor/Api/FroxlorRPC.php and FroxlorRPC::validateAuth accepts an API key and secret for an administrator or customer account without checking type_2fa, validating a TOTP code, or invoking FroxlorTwoFactorAuth. The web interface requires a second factor for accounts with two-factor authentication enabled, but the API grants access after validating only the API credentials, expiration, API permission, and account status. An attacker who obtains an API key and secret for a protected account can call the available API functions without supplying the configured second factor, which can expose or modify customer data, domains, email and FTP accounts, databases, DNS records, and certificate material. This issue is fixed in version 2.3.7.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.