Is CVE-2026-41231 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41231 being exploited in the wild.

How severe is CVE-2026-41231?

High severity, with a CVSS score of 7.5, published 23 April 2026.

Which products and versions are affected?

froxlor/froxlor (Packagist) < 2.3.6, ECOSYSTEM:introduced=0,fixed=2.3.6.

Is there a fix for CVE-2026-41231?

Yes. froxlor/froxlor (Packagist): upgrade to 2.3.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-41231?

Check whether you run Froxlor or froxlor/froxlor (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41231: Froxlor has Incomplete Symlink Validation in DataDump.add() Allows Arbitrary Directory Ownership Takeover via Cron

Q: Is there a fix for CVE-2026-41231?

Yes. froxlor/froxlor (Packagist): upgrade to 2.3.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: Am I affected by CVE-2026-41231?

Check whether you run Froxlor or froxlor/froxlor (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41231 · Severity: high · CVSS 7.5 · Published 2026-04-23

Froxlor is open source server administration software. Prior to version 2.3.6, `DataDump.add()` constructs the export destination path from user-supplied input without passing the `$fixed_homedir` parameter to `FileDir::makeCorrectDir()`, bypassing the symlink validation that was added to all other customer-facing path operations (likely as the fix for CVE-2023-6069). When the ExportCron runs as root, it executes `chown -R` on the resolved symlink target, allowing a customer to take ownership of arbitrary directories on the system. Version 2.3.6 contains an updated fix.

Technologies: Froxlor, froxlor/froxlor (Packagist). Vendors: Froxlor, Packagist.

Quick answers

Is CVE-2026-41231 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41231 being exploited in the wild.
How severe is CVE-2026-41231?: High severity, with a CVSS score of 7.5, published 23 April 2026.
Which products and versions are affected?: froxlor/froxlor (Packagist) < 2.3.6, ECOSYSTEM:introduced=0,fixed=2.3.6.
Is there a fix for CVE-2026-41231?: Yes. froxlor/froxlor (Packagist): upgrade to 2.3.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-41231?: Check whether you run Froxlor or froxlor/froxlor (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

froxlor/froxlor (Packagist): upgrade to 2.3.6 or later
```
composer require froxlor/froxlor:^2.3.6
```

Affected products

Froxlor
froxlor/froxlor (Packagist) < 2.3.6, ECOSYSTEM:introduced=0,fixed=2.3.6

Identifiers

CVE-2026-41231
GHSA-75h4-c557-j89r

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.