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