Security updates are applied to actively maintained release lines.
We strongly recommend keeping your installation up to date.
| Version | Supported |
|---|---|
| Latest stable (current production) | ✅ Fully supported |
| Active release line (e.g. 2.1.x, 2.2.x) | ✅ Supported |
| Older versions |
⚠️ Security fixes are not backported to outdated versions.
UnderHost takes security seriously. If you discover a vulnerability in cPanel Redis Manager, please report it responsibly.
Do not report security vulnerabilities through public GitHub issues.
-
Email your report to: security@underhost.com
-
Include in your report:
- Clear description of the vulnerability
- Steps to reproduce
- Potential impact
- Proof-of-concept (if applicable)
- Your name/handle for credit (optional)
-
What to expect:
- Acknowledgment within 48 hours
- Initial assessment within 5 business days
- Ongoing updates during remediation
- Credit in release notes (optional)
-
Please do not:
- Publicly disclose before a fix is released
- Access or modify data that is not yours
- Perform denial-of-service testing
The following are considered in-scope:
- cPanel and WHM plugin interfaces
- API endpoints (WHM and cPanel)
- Authentication and authorization controls
- Redis instance isolation between users
- File permissions and privilege boundaries
- Command execution and input validation
Out-of-scope:
- Misconfiguration by server administrators
- Unsupported operating systems
- Third-party software not maintained by this project
cPanel Redis Manager is designed for multi-tenant hosting environments and enforces strict isolation and privilege separation.
Each Redis instance runs under the cPanel account user and binds only to 127.0.0.1.
- No public exposure
- No cross-account access
- No shared Redis processes
All authoritative metadata is stored in: /var/lib/redis-manager/
- Owned by root
- Permission
0700 - Contains port, password, and config references
User home directories are never trusted for privileged operations.
Before any operation is performed, the process is verified:
/proc/<pid>/exemust match Redis binary- Process owner must match the cPanel account
- Command line must reference expected config file
Stale or invalid PID files are automatically detected and cleaned.
Redis configuration is generated from a strict allowlist:
maxmemorymaxmemory-policytimeout- persistence toggle
Arbitrary directives are never accepted from user input.
All state-changing actions:
- Require POST requests
- Require valid CSRF tokens
- WHM tokens are session-bound
- No shell string concatenation
- All commands executed via
proc_open()with argument arrays - Redis CLI restricted to allowlisted commands
- No world-writable files
- Config files:
0640 - Secrets and license files:
0600 - Atomic file writes used for all sensitive data
- License keys stored outside source code
- Validation results cached locally
- Grace period allows continued operation during temporary outages
- License checks enforced in both WHM and cPanel contexts
Administrative actions are logged with:
- timestamp
- actor (WHM/cPanel user)
- action performed
- target account
- result status
For support: support@underhost.com
For security disclosures: security@underhost.com