# CVE-2026-113677: Froxlor 0.10.0 before 2.3.15 Missing Authorization via SubDomains.delete API


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-9rxg-hj9r-x482, GHSA-pp2f-frcg-w8rv

## What is CVE-2026-113677?

CVE-2026-113677 is a medium-severity vulnerability in froxlor, published on 20 Oct 2026. 

### Official description

Froxlor from 0.10.0 before 2.3.15 contains a missing authorization vulnerability in the SubDomains.delete API command that allows authenticated customers to delete reseller-provisioned main domains by supplying a main domain id. Attackers can bypass the web UI restriction to remove domains, orphan vhost, DNS and subdomain records, and drive subdomains_used below zero to gain extra subdomain allowance.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-113677?


## How do I fix CVE-2026-113677?

No fix has been published for CVE-2026-113677 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113677 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113677 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113677 and fix it if it is affected.

What it is: CVE-2026-113677 is a medium-severity vulnerability in froxlor, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113677 exists.

Affected product: froxlor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113677/ (Markdown: https://insights.sbomify.com/CVE-2026-113677/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113677
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113677
- OSV: https://osv.dev/vulnerability/CVE-2026-113677

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113677/
Summaries are generated and may contain mistakes; the official description above is the record.