Quick answers
- Is CVE-2026-121436 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121436 being exploited in the wild.
- How severe is CVE-2026-121436?
- High severity, with a CVSS score of 7.2, published 3 November 2026.
- Which products and versions are affected?
- Froxlor 2.3.8 before 2.3.15.
- Is there a fix for CVE-2026-121436?
- 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-121436 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-121436?
- 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
An unscoped WHERE 1 query in api_keys.php allows any administrator with the customers_see_all flag to retrieve API keys for all users across all administrators when browsing the admin area, due to a missing owner predicate in one of three conditional branches. The detail modal then renders the full plaintext apikey and secret in the HTML response without truncation or authorization checks. The API authentication layer trusts a bare key and secret match without validating ownership, allowing the disclosed super administrator credentials to be replayed directly for authentication.
Affected products
- Froxlor Froxlor 2.3.8 before 2.3.15
Timeline
- 2026-10-20: disclosed
- 2026-11-03: advisory