CVE-2026-52793Public exploitNetwork attack vector

Protected-account access via API 2FA bypass

Published Aug 18, 2026 · Updated Aug 19, 2026

Authentication bypass in Froxlor before 2.3.7 allows remote authenticated users to invoke API functions with only an API key and secret. In lib/Froxlor/Api/FroxlorRPC.php, FroxlorRPC::validateAuth validates the key, secret, expiry, API permission, and account status but never checks type_2fa, requires a TOTP code, or calls FroxlorTwoFactorAuth for two-factor-enabled accounts. Exposure requires a valid administrator or customer API key pair for an account with 2FA enabled; once obtained, the attacker can read and modify data available through the API, including domains, email and FTP accounts, databases, DNS records, and certificate material.

CVSS severity8.1
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Froxlor before 2.3.7 allows remote authenticated users to invoke API functions with only an API key and secret. In lib/Froxlor/Api/FroxlorRPC.php, FroxlorRPC::validateAuth validates the key, secret, expiry, API permission, and account status but never checks type_2fa, requires a TOTP code, or calls FroxlorTwoFactorAuth for two-factor-enabled accounts. Exposure requires a valid administrator or customer API key pair for an account with 2FA enabled; once obtained, the attacker can read and modify data available through the API, including domains, email and FTP accounts, databases, DNS records, and certificate material.

The record

CVE
CVE-2026-52793
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Froxlor
Product
Froxlor
Classifications
CWE-287, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=<.3.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Froxlor · Froxlorversion=<.3.7

Published CVSS scores

8.1GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-287Improper Authentication
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo