Attack Chain

1. Initial Access: A low-privilege authenticated user gains access to the HestiaCP administration panel, typically through legitimate credentials or by compromising such credentials.
2. Input Submission: The authenticated user navigates to the DNS management section within the HestiaCP panel and attempts to create or modify a DNS record, specifically targeting a field where DNS record types are expected.
3. Command Injection: The user crafts a malicious payload containing a single-quote character (') and injects it into the vulnerable DNS record type field, designed to break out of expected string assignments.
4. Input Validation Bypass: The HestiaCP function is_dns_record_format_valid() fails to properly sanitize or validate the malicious input, allowing the injected single-quote character and the subsequent command payload to pass through.
5. Unsafe Parsing: The update_domain_zone() function processes the unvalidated input using an eval-based parsing mechanism. This unsafe evaluation interprets the injected malicious payload as executable code rather than a literal string.
6. Root Command Execution: HestiaCP executes the attacker's arbitrary commands directly on the underlying Linux host, inheriting root privileges due to the context of the HestiaCP process.
7. System Compromise: With root-level command execution, the attacker achieves full control over the host system, enabling them to install backdoors, exfiltrate sensitive data, deploy malware, or further pivot within the network.

Impact

The successful exploitation of CVE-2025-30007 grants low-privilege authenticated users complete root access to the underlying HestiaCP server. This severe impact means an attacker can take full control of the operating system, including all hosted websites, databases, and sensitive configuration files. Potential consequences include unauthorized data exfiltration, installation of persistent backdoors, deployment of ransomware, or the use of the compromised server as a platform for further attacks. This could lead to significant financial losses, reputational damage, and regulatory penalties for affected organizations.

Recommendation

• Immediately update HestiaCP to version 1.9.5 or later to patch CVE-2025-30007.
• Review web server access logs for HestiaCP administration interfaces for unusual authentication patterns or attempts from unknown IPs.
• Monitor system process creation logs on HestiaCP servers for processes spawned by the HestiaCP user (e.g., www-data, nginx) that are not part of normal operations, especially those indicative of shell commands or reverse shells.