Is CVE-2026-41235 exploited in the wild?

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

How severe is CVE-2026-41235?

High severity, with a CVSS score of 8.8, published 4 June 2026.

Which products and versions are affected?

Froxlor 2.3.6; froxlor/froxlor (Packagist) = 2.3.6, ECOSYSTEM:introduced=2.3.6,fixed=2.3.7.

Is there a fix for CVE-2026-41235?

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

How is CVE-2026-41235 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-41235?

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-41235: Froxlor incorrect authorization in FTP shell assignment

CVE-2026-41235 · Severity: high · CVSS 8.8 · Published 2026-06-04

Froxlor is an open-source server management panel used to administer web hosting environments. A security flaw allows customers with FTP access to bypass administrative restrictions and assign themselves a full system command shell (such as /bin/bash) even when the administrator has restricted them to limited options. This allows a low-privileged user to gain interactive access to the underlying server, potentially leading to data theft, service disruption, or further attacks on the hosting infrastructure.

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

Quick answers

Is CVE-2026-41235 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41235 being exploited in the wild.
How severe is CVE-2026-41235?: High severity, with a CVSS score of 8.8, published 4 June 2026.
Which products and versions are affected?: Froxlor 2.3.6; froxlor/froxlor (Packagist) = 2.3.6, ECOSYSTEM:introduced=2.3.6,fixed=2.3.7.
Is there a fix for CVE-2026-41235?: Yes. froxlor/froxlor (Packagist): upgrade to 2.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41235 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41235?: 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.7 or later
```
composer require froxlor/froxlor:^2.3.7
```

Technical details

An incorrect authorization vulnerability exists in Froxlor 2.3.6 due to missing server-side validation of the shell parameter in the Ftps.add and Ftps.update API handlers. While the web interface restricts shell selection based on the 'system.available_shells' configuration, the backend only performs generic string validation and does not check the input against the administrator-defined whitelist. In deployments using the default 'nssextrausers' integration, an authenticated customer with shell delegation enabled can submit a request with an arbitrary shell (e.g., /bin/bash). This value is then propagated by a root-owned cron task into the system's passwd database, granting the attacker interactive shell access to the host. The issue is resolved in version 2.3.7.

Affected products

Froxlor Froxlor 2.3.6

Identifiers

CVE-2026-41235
GHSA-gcv3-5v9q-fmhh

Timeline

2026-05-15: patched: Version 2.3.7 released
2026-05-29: advisory: GitHub Security Advisory published
2026-06-04: disclosed: CVE published to NVD

References

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