# CVE-2026-100716: Froxlor before 2.3.12 Privilege Escalation via Symlink

> Authenticated users can escalate privileges to root by exploiting a symlink vulnerability in the data-export cron job, compromising the host system.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-2wjc-6mgx-hq42, GHSA-x52g-rfx2-v8v7

## What is CVE-2026-100716?

CVE-2026-100716 is a critical path traversal vulnerability in froxlor, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Froxlor is a server administration panel. In versions 2.3.10 and earlier, the customer data-export (DataDump) cron fails to validate intermediate path components of the export destination: Froxlor\FileDir::makeCorrectDir() contains an off-by-one in its path-component walk that skips the first segment below the customer home directory, and the guard in ExportCron.php checks only the final component with is_link(). An authenticated customer whose account has the export feature enabled can schedule an export into a genuine subdirectory of their own webspace, then replace an intermediate path component with a symlink before the root-owned cron runs. The cron's `chown -R` then recursively changes ownership of the linked directory tree — for example /etc — to the customer's UID, yielding host root and cross-tenant compromise. Exploitation is deterministic and requires no race. This is an incomplete fix of GHSA-75h4-... The issue is fixed in Froxlor 2.3.12.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-100716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100716 is a critical path traversal vulnerability in froxlor, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100716 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-100716/ (Markdown: https://insights.sbomify.com/CVE-2026-100716/index.md)
```

## Sources

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

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