Is CVE-2026-113677 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-113677 being exploited in the wild.

How severe is CVE-2026-113677?

Medium severity, with a CVSS score of 5.4, published 20 October 2026.

Is there a fix for CVE-2026-113677?

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-113677 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-113677?

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.

CVE-2026-113677: Froxlor missing authorization in SubDomains.delete API

CVE-2026-113677 · Severity: medium · CVSS 5.4 · Published 2026-10-20

Froxlor is a web hosting control panel that manages domains, subdomains, and associated infrastructure. An authenticated customer can exploit a missing authorization check in the SubDomains.delete API command to delete main domains assigned to them by resellers, orphaning vhosts, DNS records, and subdomains while artificially lowering the customer's subdomain quota to gain extra allocations.

Technologies: Froxlor. Vendors: Froxlor.

Quick answers

Is CVE-2026-113677 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-113677 being exploited in the wild.
How severe is CVE-2026-113677?: Medium severity, with a CVSS score of 5.4, published 20 October 2026.
Which products and versions are affected?: Froxlor 0.10.0 to 2.3.14.
Is there a fix for CVE-2026-113677?: 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-113677 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-113677?: 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 SubDomains.delete API endpoint fails to verify ownership restrictions when a customer attempts to delete a main domain (parentdomainid=0) rather than a subdomain. An authenticated customer can bypass the web UI restriction by directly calling the API with a main domain ID, deleting domains owned by resellers and corrupting quota tracking by driving subdomains_used negative. The fix enforces a check to prevent non-admin users from deleting resources with parentdomainid=0.

Affected products

Froxlor Froxlor 0.10.0 to 2.3.14

Timeline

2026-10-20: disclosed
2026-10-20: patched: CVE-2026-113677; fix applied in commit 078e3f4

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.