Quick answers
- Is CVE-2026-109962 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109962 being exploited in the wild.
- How severe is CVE-2026-109962?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Froxlor 0.10.0 before 2.3.14.
- Is there a fix for CVE-2026-109962?
- Yes: fixed in 2.3.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109962 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109962?
- 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.14
Technical details
The MysqlServer and Cronjobs API read commands (listing, get, listingCount) fail to enforce the change_serversettings permission check that their write counterparts use, relying only on isAdmin() which returns true for both full admins and resellers. A reseller can call these API endpoints via api.php to retrieve full server configuration details including management usernames, hosts, ports, and TLS settings that are deliberately withheld from the web UI. Passwords are stripped from responses, but other infrastructure metadata is fully disclosed.
Affected products
- Froxlor Froxlor 0.10.0 before 2.3.14
Timeline
- 2026-09-29: disclosed
- 2026-10-13: advisory