CVE-2026-52793
API 2FA bypass in Froxlor allows account access using API key/secret.
Is CVE-2026-52793 being exploited?
Not confirmed. CVE-2026-52793 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-52793?
CVE-2026-52793 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-52793?
Yes. A fix has been recorded for CVE-2026-52793. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-52793 affect?
CVE-2026-52793 affects Froxlor < 2.3.7, Froxlor API (FroxlorRPC). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-52793?
Upgrade to Froxlor 2.3.7+, rotate API keys/secrets, audit API access and logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
API authentication bypasses TOTP 2FA; attacker with API key/secret can read/modify customers, domains, mail/FTP, DBs, DNS, and certificates.
Immediate action required