Quick answers
- Is CVE-2026-121435 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121435 being exploited in the wild.
- How severe is CVE-2026-121435?
- Medium severity, with a CVSS score of 4.3, published 3 November 2026.
- Which products and versions are affected?
- Froxlor before 2.3.15.
- Is there a fix for CVE-2026-121435?
- 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-121435 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-121435?
- 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 Mysqls::add() API endpoint in Froxlor lacks the customer_hide_options authorization check present in the get(), update(), and delete() methods, allowing authenticated customers to bypass the admin policy that hides or disables MySQL for them. The vulnerability requires low privilege (authenticated customer access) and can be exploited remotely via API calls with no user interaction. The fix adds the missing authorization check to the add() method.
Affected products
- Froxlor Froxlor before 2.3.15
Timeline
- 2026-10-20: disclosed
- 2026-11-03: advisory