When using CloudPanel File Manager to change permissions recursively on a directory, the system incorrectly applies the same permission mode to both directories and files
Specifically, when setting a directory to 770, all contained files are also set to 770, instead of using appropriate file permissions.
Impact:
This suggests the recursive permission logic is applying directory mode to files, instead of distinguishing between:
Medium to High (incorrect permission handling with security implications)
Specifically, when setting a directory to 770, all contained files are also set to 770, instead of using appropriate file permissions.
Impact:
- Incorrect file permissions
- Potential security risk
- Breaks standard permission models for WordPress and Linux systems
This suggests the recursive permission logic is applying directory mode to files, instead of distinguishing between:
- chmod for directories
- chmod for files
Medium to High (incorrect permission handling with security implications)
How to reproduc
- Open CloudPanel File Manager
- Select a folder (e.g. WordPress theme directory)
- Change permissions to 770
- Inspect files inside the folder
- Directories → 770
- Files → 660 (or remain unchanged
Possible Solution
Suggestion:- Separate handling for files vs directories during recursive chmod
- Apply:
- directories → requested mode
- files → safe default (e.g. 644/660) or leave unchanged
Additional Context
- OS: Ubuntu 24.04
- CloudPanel: v2.5.3
- PHP: 8.5
- WordPress: latest (observed across multiple installations)