CVE-2026-26279
Input Validation Bypass in Froxlor Enables Root Remote Code Execution
Publication date: 2026-03-03
Last updated on: 2026-03-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| froxlor | froxlor | to 2.3.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
| CWE-482 | The code uses an operator for comparison when the intention was to perform an assignment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Froxlor, an open source server administration software, in versions prior to 2.3.4. Due to a typo in the input validation code (using '==' instead of '='), the software completely disables email format checking for fields declared as email type. This allows an authenticated admin user to store arbitrary strings in the panel.adminmail setting.
Later, this stored value is concatenated into a shell command executed as root by a cron job. Since the pipe character '|' is explicitly whitelisted, an attacker can exploit this to execute arbitrary commands with root privileges, resulting in full root-level Remote Code Execution (RCE).
This vulnerability was fixed in Froxlor version 2.3.4.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an authenticated administrator to execute arbitrary commands with root privileges on the server running Froxlor.
An attacker exploiting this flaw can gain full control over the affected system, potentially leading to data theft, data loss, service disruption, installation of malware, or further attacks within the network.
Since the attack requires authenticated admin access, the risk is higher if admin credentials are compromised or if there are multiple administrators with access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in Froxlor version 2.3.4. Immediate mitigation involves upgrading Froxlor to version 2.3.4 or later.
Since the vulnerability allows an authenticated admin to inject arbitrary strings into the panel.adminmail setting, restricting admin access and reviewing this setting for suspicious values can help reduce risk until the upgrade is applied.