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.
CVE-2026-100716
Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-26. A secondary CVSS source baseline 9.9; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9CRITICALhigh confidence
- EG Risk
- 61EG Risk 61/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 31st
- KEV
- Not listed
CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 26, 2026
Last Modified
September 28, 2026
Advisory Details (2)
Auto-updated Sep 28, 2026DataDump export cron follows intermediate symlinks — customer gains ownership of arbitrary directories via root `chown -R` (incomplete fix of GHSA-75h4) · Advisory · froxlor/froxlor · GitHub
https://github.com/froxlor/froxlor/security/advisories/GHSA-2wjc-6mgx-hq42Froxlor before 2.3.12 Privilege Escalation via Symlink | Advisories | VulnCheck
https://www.vulncheck.com/advisories/froxlor-before-2.3.12-privilege-escalation-via-symlinkVendor Advisories for CVE-2026-100716(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 53× in last 7d / 62× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 08:51 UTCGHSA enrichment
- 2026-10-04 04:29 UTCGHSA enrichment
- 2026-10-04 00:08 UTCGHSA enrichment
- 2026-10-03 19:46 UTCGHSA enrichment
- 2026-10-03 15:26 UTCEG score recompute
- 2026-10-03 15:25 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 11:00 UTCGHSA enrichment
- 2026-10-03 06:39 UTCGHSA enrichment
- 2026-10-03 02:18 UTCGHSA enrichment
- 2026-10-02 21:55 UTCGHSA enrichment
- 2026-10-02 17:35 UTCEG score recompute
- 2026-10-02 17:35 UTCGHSA enrichment
- 2026-10-02 13:14 UTCGHSA enrichment
- 2026-10-02 08:52 UTCGHSA enrichment
- 2026-10-02 04:27 UTCGHSA enrichment
- 2026-10-02 00:02 UTCEG score recompute
- 2026-10-02 00:02 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 19:24 UTCGHSA enrichment
- 2026-10-01 15:04 UTCGHSA enrichment
- 2026-10-01 10:43 UTCGHSA enrichment
- 2026-10-01 06:22 UTCGHSA enrichment
- 2026-10-01 02:01 UTCGHSA enrichment
- 2026-09-30 21:34 UTCGHSA enrichment
Show 37 moreShow fewer
- 2026-09-30 17:10 UTCEG score recompute
- 2026-09-30 17:10 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-30 12:50 UTCGHSA enrichment
- 2026-09-30 08:29 UTCGHSA enrichment
- 2026-09-30 04:08 UTCGHSA enrichment
- 2026-09-29 23:47 UTCGHSA enrichment
- 2026-09-29 18:12 UTCEG score recompute
- 2026-09-29 18:12 UTCGHSA enrichment
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-29 13:13 UTCGHSA enrichment
- 2026-09-29 08:52 UTCGHSA enrichment
- 2026-09-29 04:32 UTCGHSA enrichment
- 2026-09-29 00:10 UTCEG score recompute
- 2026-09-29 00:10 UTCGHSA enrichment
- 2026-09-28 19:49 UTCEG score recompute
- 2026-09-28 19:49 UTCGHSA enrichment
- 2026-09-28 15:27 UTCEG score recompute
- 2026-09-28 15:26 UTCGHSA enrichment
- 2026-09-28 14:57 UTCEG score recompute
- 2026-09-28 14:57 UTCGHSA enrichment
- 2026-09-28 14:19 UTCGHSA enrichment
- 2026-09-28 09:58 UTCGHSA enrichment
- 2026-09-28 05:38 UTCGHSA enrichment
- 2026-09-28 01:17 UTCGHSA enrichment
- 2026-09-27 20:56 UTCGHSA enrichment
- 2026-09-27 16:36 UTCEG score recompute
- 2026-09-27 16:36 UTCGHSA enrichment
- 2026-09-27 12:15 UTCGHSA enrichment
- 2026-09-27 07:54 UTCGHSA enrichment
- 2026-09-27 03:33 UTCGHSA enrichment
- 2026-09-26 23:08 UTCGHSA enrichment
- 2026-09-26 18:46 UTCEG score recompute
- 2026-09-26 18:46 UTCGHSA enrichment
- 2026-09-26 14:25 UTCEG score recompute
- 2026-09-26 13:33 UTCEG score recompute
- 2026-09-26 13:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-100716?
When was CVE-2026-100716 disclosed?
Is CVE-2026-100716 actively exploited?
What is the CVSS score of CVE-2026-100716?
How do I remediate CVE-2026-100716?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-100716
Is Your Infrastructure Affected by CVE-2026-100716?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.