# CVE-2026-121434: Froxlor Certificates API authorization bypass in Let's Encrypt management

Source: https://junglewise.ai/threats/cve-2026-121434-froxlor-2-3-0-before-2-3-15-contains-a-missing-authorization  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-121434 · Severity: medium · CVSS 5.4 · Published 2026-11-03

Froxlor is a hosting control panel that automates SSL certificate management via Let's Encrypt. An API authorization flaw allows customers with API access to overwrite their domain's Let's Encrypt-managed certificates and private keys with attacker-controlled ones. When deployed by the panel's automation, this breaks HTTPS for the domain and disrupts the ACME certificate renewal process.

Technologies: [Froxlor](https://junglewise.ai/threats/technologies/froxlor). Vendors: [Froxlor](https://junglewise.ai/threats/vendors/froxlor).

## Quick answers

**Is CVE-2026-121434 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-121434 being exploited in the wild.

**How severe is CVE-2026-121434?** Medium severity, with a CVSS score of 5.4, published 3 November 2026.

**Which products and versions are affected?** Froxlor 2.3.0 through 2.3.14.

**Is there a fix for CVE-2026-121434?** Yes: fixed in 2.3.15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-121434 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-121434?** Check whether you run Froxlor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.3.15

## Technical details

The Certificates.add and Certificates.update API commands lack authorization checks to verify whether a domain's certificate is Let's Encrypt-managed, in contrast to read-path fixes applied in 2.3.13. An authenticated API customer can silently replace a server-managed certificate and private key via these endpoints, which are then deployed to the webserver via a REBUILD_VHOST task. The vulnerability affects versions 2.3.0 through 2.3.14; authentication and API access are required.

## Affected products

- Froxlor Froxlor 2.3.0 through 2.3.14

## Timeline

- 2026-10-20: disclosed
- 2026-11-03: advisory

## References

- [https://github.com/froxlor/froxlor/security/advisories/GHSA-ch7m-649m-x7xg](https://github.com/froxlor/froxlor/security/advisories/GHSA-ch7m-649m-x7xg)
- [https://www.vulncheck.com/advisories/froxlor-2.3.0-before-2.3.15-authorization-bypass-via-certificates-update-api](https://www.vulncheck.com/advisories/froxlor-2.3.0-before-2.3.15-authorization-bypass-via-certificates-update-api)

## Related threats

- [Froxlor information disclosure in API keys listing](https://junglewise.ai/threats/cve-2026-121436-froxlor-from-2-3-8-before-2-3-15-contains-an-information)
- [Froxlor authorization bypass in Mysqls.add API](https://junglewise.ai/threats/cve-2026-121435-froxlor-before-2-3-15-contains-an-authorization-bypass)
- [Froxlor symlink following in Statistics::makeChownWithNewStats](https://junglewise.ai/threats/cve-2026-113678-froxlor-before-2-3-15-contains-a-symlink-following-vulnerability)
- [Froxlor missing authorization in SubDomains.delete API](https://junglewise.ai/threats/cve-2026-113677-froxlor-from-0-10-0-before-2-3-15-contains-a-missing)
- [Froxlor authorization bypass in Admins.get API](https://junglewise.ai/threats/cve-2026-113676-froxlor-from-0-10-0-before-2-3-15-contains-an-authorization)