Quick answers
- Is CVE-2026-113676 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113676 being exploited in the wild.
- How severe is CVE-2026-113676?
- Medium severity, with a CVSS score of 4.3, published 20 October 2026.
- Which products and versions are affected?
- Froxlor 0.10.0 before 2.3.15.
- Is there a fix for CVE-2026-113676?
- 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-113676 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-113676?
- 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 authorization bypass exists in the Admins.get API command due to identifier confusion: a reseller can supply their own loginname paired with another admin's numeric ID, causing the authorization check to pass (which uses OR logic) while the subsequent database query executes against the attacker-supplied ID alone. This allows a reseller to enumerate and retrieve full records of any admin. The vulnerability requires API access and affects versions 0.10.0 through 2.3.14.
Affected products
- Froxlor Froxlor 0.10.0 before 2.3.15
Timeline
- 2026-10-20: disclosed