Critical vulnerability
Critical vulnerability in Hestia Control Panel (GHSA-p4vq-6v6h-cc74)
Hestia Control Panel · Servers and applications
GHSA-p4vq-6v6h-cc74
HestiaCP's read-only enforcement for protected-admin sessions misses its POST endpoints, letting a secondary admin mint root-level API keys and switch off the protection itself
- Severity
- Critical 9.6
- Published
- 14 Nov 2026
- Fixed in
- 1.10.6
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
All evidence, reproduction steps, and scripts in the report were verified against a real running instance. Nothing is fabricated or synthetic; every verdict is backed by captured output from an actual deployment.
HestiaCP protects its main administrator (the ROOT_USER, default admin) with POLICY_SYSTEM_PROTECTED_ADMIN (enabled by default): when another administrator uses the "login as" feature to operate the ROOT_USER's account, the session is forced read-only and no write may occur. Release 1.10.5 enforces that rule on roughly twenty individual add/edit pages, but the enforcement is page-by-page and the POST handlers of most write endpoints have no check at all.
| Software | Affected versions |
|---|---|
| Hestia Control PanelServers and applications |
|
- GitHub Advisory Database https://github.com/advisories/GHSA-p4vq-6v6h-cc74
- github.com https://github.com/hestiacp/hestiacp/security/advisories/GHSA-p4vq-6v6h-cc74
From NVD, the CVE Program, OSV.dev with the GitHub Advisory Database, WPVulnerability, WordPress's security advisories and CISA's Known Exploited Vulnerabilities catalog, as they stood when this was written. Each vulnerability's own page has its latest rating and fix. This product uses the NVD API but is not endorsed or certified by the NVD.