Quick answers
- Is CVE-2025-30007 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-30007 being exploited in the wild.
- How severe is CVE-2025-30007?
- High severity, with a CVSS score of 8.8, published 10 July 2026.
- Which products and versions are affected?
- HestiaCP < 1.9.5.
- Is there a fix for CVE-2025-30007?
- A patch was published on 2026-01-04: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-30007 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-30007?
- Check whether you run HestiaCP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authenticated OS command injection vulnerability exists in HestiaCP versions prior to 1.9.5. The flaw stems from insufficient input validation in the 'is_dns_record_format_valid()' function combined with unsafe eval-based parsing within 'update_domain_zone()'. By injecting a single-quote character into specific DNS record types, an attacker can prematurely close a variable assignment string to execute arbitrary shell commands. This allows a low-privilege authenticated user to achieve full root code execution on the underlying host. The issue is addressed in version 1.9.5 by hardening DNS record validation.
Affected products
- HestiaCP HestiaCP < 1.9.5
Timeline
- 2025-12-23: other: Initial pull request for hardening DNS validation submitted
- 2026-01-04: patched: Fix merged into main branch
- 2026-05-28: advisory: Release 1.9.5 published
- 2026-07-10: disclosed: CVE-2025-30007 published