Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconAuthenticate as customer
-
DeliveryCreate symlink to target directory
-
ExploitTrigger export via panel
-
InstallWait for ExportCron execution
-
C2chown follows symlink
-
ExecuteModify owned system files
-
ImpactEscalate to root access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires authenticated customer account access to the Froxlor administration panel. The Froxlor installation must have the ExportCron scheduled task configured and running with root privileges (common default for hosting environments to enable backup and export features across customer file boundaries). Exploitation requires the attacker to create symbolic links in their accessible filesystem locations (typically the customer's home directory or web root) pointing to target system directories. Attack success depends on timing-the symlink must exist when ExportCron processes the export job. Attack complexity is high (CVSS AC:H) because the attacker must predict or influence the export path construction and coordinate with the cron schedule. However, limiting factors are significant: not all Froxlor deployments run ExportCron as root (some use restricted service accounts), the feature may be disabled in security-hardened configurations, and filesystem permissions or mandatory access controls (SELinux/AppArmor) may prevent symlink creation or following. The vulnerability is specific to installations where customers have file-level access combined with administrative panel features-typical in shared hosting but less common in managed or containerized environments. |
| Impact | The CVSS score of 7.5 (High) reflects network attack vector with high attack complexity, requiring low privileges and no user interaction, with high impact to confidentiality, integrity, and availability. However, real-world risk assessment requires nuanced analysis. Attack complexity is rated high (AC:H) likely because exploitation requires: (1) authenticated customer account, (2) timing the symlink creation before the ExportCron executes, (3) predicting the export path construction, and (4) the cron running as root (deployment-dependent). The privilege requirement (PR:L) indicates any authenticated customer can attempt exploitation-a significant concern in multi-tenant hosting environments where Froxlor is commonly deployed. The technical impact is severe: arbitrary directory ownership changes could lead to complete system compromise by taking ownership of /etc/shadow for password changes, /root/.ssh for SSH access, or web server directories for code injection. EPSS score unavailable-likely because this is a 2026 CVE identifier (future year, possibly data entry error or pre-disclosure). No CISA KEV listing suggests no confirmed widespread exploitation, but the vulnerability class (symlink following in SUID/root processes) has extensive exploitation history. This represents a regression vulnerability where incomplete fix application creates exploitable gaps-a pattern that often receives focused attention from attackers familiar with the original CVE-2023-6069. Priority should be HIGH for any Froxlor installation in multi-customer hosting environments where the ExportCron runs with elevated privileges. |
| Exploit ScenarioDerived | An authenticated customer with a basic hosting account on a Froxlor-managed server creates a symbolic link in their home directory pointing to /etc/shadow. They then trigger a data export operation through the Froxlor panel, specifying the symlink path as the export destination. When the scheduled ExportCron task executes as root, it constructs the export path from the customer's input without validating symlinks, then runs 'chown -R customer:customer' on the resolved path-following the symlink to /etc/shadow. The attacker now owns the system password file, can modify root credentials, and achieves full system compromise. From there, they can pivot to other customer accounts, exfiltrate data from the entire hosting infrastructure, or establish persistent backdoor access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 23, 2026
Symlink-based privilege escalation in Froxlor versions prior to 2.3.6 allows authenticated customers to gain ownership of arbitrary system directories. When the ExportCron executes as root, it performs 'chown -R' on user-controlled export paths that bypass symlink validation (introduced to fix CVE-2023-6069), enabling attackers to place symbolic links and hijack ownership of critical system files. This is a regression of the CVE-2023-6069 fix where DataDump.add() failed to apply the same symlink protections used elsewhere. EPSS data unavailable; no evidence of active exploitation (not in CISA KEV), but the specific vulnerability class (symlink following in privileged operations) has well-known exploitation patterns. Patch available in version 2.3.6.
RemediationAI
Upgrade immediately to Froxlor version 2.3.6, released with the fix documented in commit 2987b0e8806ef12b532410050ad76d13d673a87d (https://github.com/froxlor/froxlor/commit/2987b0e8806ef12b532410050ad76d13d673a87d). The patch properly passes the $fixed_homedir parameter to FileDir::makeCorrectDir() to enforce symlink validation in DataDump.add(), closing the gap left by the CVE-2023-6069 remediation. Release notes and changelog available at https://github.com/froxlor/froxlor/releases/tag/2.3.6. If immediate patching is not feasible, implement compensating controls: disable the ExportCron feature entirely (blocks all data export functionality-impacts backup workflows), run ExportCron under a restricted service account rather than root (reduces impact to that account's permissions but may break legitimate file operations requiring elevated access), implement mandatory access controls (SELinux/AppArmor) to prevent ownership changes of system directories (adds operational complexity and requires policy development), or restrict customer access to export functionality through configuration (may not be enforceable if customers have panel access). Each workaround has significant operational trade-offs; vendor patch is the only complete solution.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Froxlor is a server administration panel for managing web hosting resources. The vulnerability exists in the DataDump.add() function which constructs export destination paths from customer input. The code fails to pass the $fixed_homedir parameter to FileDir::makeCorrectDir(), a symlink validation mechanism that was added to other customer-facing path operations as remediation for CVE-2023-6069 (a prior path traversal/symlink vulnerability). CWE-59 (Improper Link Resolution Before File Access, 'Link Following') describes this class of Time-of-Check-Time-of-Use (TOCTOU) race conditions where an attacker creates symbolic links pointing to sensitive locations. When Froxlor's ExportCron scheduled task runs with root privileges to perform data exports, it executes 'chown -R' (recursive ownership change) on the path constructed from user input. Because symlink validation was bypassed, the chown operation follows the symlink to its target, changing ownership of whatever directory the customer's symlink points to-potentially /etc, /root, /var/www, or other critical system paths.
Know when Froxlor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
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.
Executive ViewAI
Froxlor versions before 2.3.6 contain a privilege escalation vulnerability that allows authenticated customers to gain unauthorized ownership of critical system directories through symlink manipulation. This regression in security controls could enable attackers to compromise system integrity and potentially escalate privileges beyond their authorized scope, affecting organizations hosting multiple customer instances.
Apply vendor patch to version 2.3.6 or later. Interim mitigations if patching is delayed: restrict ExportCron execution privileges; implement strict input validation on customer-supplied export paths; enforce symlink traversal protections at the filesystem level; monitor and log all chown operations initiated by Froxlor processes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8. Rated high severity (CVSS 8.8), this vulnerabilit
Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20. Rated cr
Authentication Bypass by Primary Weakness in GitHub repository froxlor/froxlor prior to 2.0.13. Rated critical severity
Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name. Rated critic
Command injection in Froxlor server admin before 2.3.4 due to typo (== instead of =) disabling input validation entirely
Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0. Rated high severity (CV
Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14. Rated high severit
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8),
Code Injection in GitHub repository froxlor/froxlor prior to 2.0.11. Rated high severity (CVSS 8.8), this vulnerability
Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10. Rated high severity (CVSS 8.8), this vulnerability
An issue was discovered in Froxlor before 0.10.14. Rated high severity (CVSS 8.8), this vulnerability is remotely exploi
Froxlor is open source server administration software. Rated high severity (CVSS 7.5), this vulnerability is remotely ex
EUVD-2026-25182
GHSA-75h4-c557-j89r
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB