# CVE-2026-26279: Froxlor Admin-to-Root Privilege Escalation via Input Validation Bypass + OS Command Injection

> An authenticated admin can achieve root-level remote code execution by bypassing email validation to inject commands into a cron job.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-33mp-8p67-xj7c

## What is CVE-2026-26279?

CVE-2026-26279 is a critical command injection vulnerability in Froxlor, published on 3 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Froxlor is open source server administration software. Prior to 2.3.4, a typo in Froxlor's input validation code (== instead of =) completely disables email format checking for all settings fields declared as email type. This allows an authenticated admin to store arbitrary strings in the panel.adminmail setting. This value is later concatenated into a shell command executed as root by a cron job, where the pipe character | is explicitly whitelisted. The result is full root-level Remote Code Execution. This vulnerability is fixed in 2.3.4.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-482 (Comparing instead of Assigning)

## Which versions are affected by CVE-2026-26279?

2 open source packages ship an affected version, including froxlor/froxlor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `froxlor/froxlor` | Packagist | All versions | 2.3.4 |
| `froxlor/froxlor` | Packagist | All versions | 2.3.4 |

Products: Froxlor Froxlor.

## How do I fix CVE-2026-26279?

Upgrade froxlor/froxlor to 2.3.4 or later.

## Is CVE-2026-26279 being exploited?

There is no known exploitation of CVE-2026-26279 in the wild and no public exploit code.

## Other vulnerabilities in Froxlor

- [CVE-2026-41228](https://insights.sbomify.com/CVE-2026-41228/): Froxlor has Local File Inclusion via path traversal in API `def_language` parameter that leads to Remote Code Execution (critical 10.0)
- [CVE-2023-6069](https://insights.sbomify.com/CVE-2023-6069/): Improper Link Resolution Before File Access in froxlor/froxlor (critical 9.9)
- [CVE-2023-0671](https://insights.sbomify.com/CVE-2023-0671/): Code Injection in froxlor/froxlor (critical 9.9)
- [CVE-2023-3173](https://insights.sbomify.com/CVE-2023-3173/): Improper Restriction of Excessive Authentication Attempts in froxlor/froxlor (critical 9.8)
- [CVE-2023-1307](https://insights.sbomify.com/CVE-2023-1307/): Authentication Bypass by Primary Weakness in froxlor/froxlor (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26279 and fix it if it is affected.

What it is: CVE-2026-26279 is a critical command injection vulnerability in Froxlor, published on 3 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26279 in the wild and no public exploit code.

Affected packages and fixed versions:
- froxlor/froxlor (Packagist): affected all versions; fixed in 2.3.4
- froxlor/froxlor (Packagist): affected all versions; fixed in 2.3.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26279/ (Markdown: https://insights.sbomify.com/CVE-2026-26279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26279
- OSV: https://osv.dev/vulnerability/CVE-2026-26279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26279/
Summaries are generated and may contain mistakes; the official description above is the record.