CVE-2026-100716: froxlor · In versions 2.3.10 and earlier, the customer data-export (DataDump) cron fails to validate intermediate path components of the export destination
Affects froxlorSource GCVE Database
Not known to be exploited · CVSS 9.9 Critical · fixed in 2.3.12 : patch froxlor as a priority.
Data as of 11 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfroxlor/froxlorpkg:github/froxlor/froxlorOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Froxlor to version 2.3.12 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause of the path validation and symlink handling issues.
Description
Froxlor versions 2.3.10 and earlier contain a critical vulnerability in the customer data-export cron job. The vulnerability arises from improper validation of intermediate path components in the export destination, allowing an authenticated customer to create symlinks that cause the cron job to recursively change ownership of arbitrary directories, including sensitive system paths. This can lead to host root and cross-tenant compromise. The issue is fixed in Froxlor version 2.3.12.