Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Froxlor versions before 2.3.6 are affected. In DataDump.add(), the export destination path built from user input skips the symlink validation applied to other customer path operations. A customer with API access and the export feature enabled can create a symlink so that the root-run export cron recursively changes ownership of an arbitrary directory, which can lead to read and write access to other customers' data or system files. Upgrade to Froxlor 2.3.6 or later, which contains the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0041, the 36th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 23 Apr 2026, 04:16 UTC Confirmed by NVD
- 31 Oct 2026, 14:25 UTC First seen by agentprime
- 31 Oct 2026, 14:25 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-75h4-c557-j89r
- OSV: GHSA-75h4-c557-j89r
- github.com/froxlor/froxlor/security/advisories/GHSA-75h4-c557-j89r
- nvd.nist.gov/vuln/detail/CVE-2026-41231
- github.com/froxlor/froxlor/commit/2987b0e8806ef12b532410050ad76d13d673a87d
- github.com/froxlor/froxlor
- github.com/froxlor/froxlor/releases/tag/2.3.6