dbcve.org
Control PanelApplication · Hestiacp

CVE-2025-30007

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.9.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HestiaCP before 1.9.5 contains an authenticated OS command injection vulnerability that allows low-privilege authenticated users to execute arbitrary commands as root by injecting a single-quote character into unvalidated DNS record types. Attackers can exploit insufficient input validation in is_dns_record_format_valid() combined with unsafe eval-based parsing in update_domain_zone() to prematurely close a variable assignment string and achieve full root code execution on the underlying host in a single DNS record creation step.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated OS command injection in HestiaCP before v1.9.5 allows low-privilege users to achieve root code execution by injecting a single-quote into DNS record type fields. The vulnerability chains insufficient input validation in is_dns_record_format_valid() with unsafe eval-based parsing in update_domain_zone(), enabling attackers to prematurely close variable assignment strings and execute arbitrary commands as root via a single DNS record creation request.

MitigationUpgrade to HestiaCP 1.9.5 or later. Additionally, implement proper input validation with parameterized queries or avoid eval usage entirely in DNS record processing functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Control PanelApplication
Affected:< 1.9.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Hestiacp version
    Run 'v-list-sys-info' or check /usr/local/hestia/include/version 2>/dev/null; cat /usr/local/hestia/include/version
    Affected if Version is below 1.9.5 (versions like 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.9.4 are affected)
  2. Verify DNS feature is enabled
    Run 'v-list-user admin' or check the user configuration to see if DNS is listed among enabled features
    Affected if DNS feature is enabled for any user on the system
  3. Inspect DNS record validation function
    Locate the is_dns_record_format_valid() function in the Hestiacp source code, typically in /usr/local/hestia/func/ or /usr/local/hestia/web/inc/core/
    Affected if The function uses insufficient input validation or lacks proper sanitization of DNS record type fields
  4. Inspect DNS zone update function
    Locate the update_domain_zone() function in the Hestiacp source code, typically in /usr/local/hestia/func/
    Affected if The function uses eval or similar unsafe parsing methods to process DNS record data
  5. Check user privilege configuration
    Review user account configurations via 'v-list-users' to identify low-privilege user accounts that have DNS management access
    Affected if Low-privilege (non-admin) users have permissions to create or modify DNS zones

A system is affected if it runs Hestiacp below version 1.9.5, has the DNS feature enabled, and allows any authenticated user to manage DNS records through the vulnerable validation and update functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.5 or later
Fixed in 1.9.5
Vendor patch github.com →
Interim mitigation

Upgrade to HestiaCP 1.9.5 or later. Additionally, implement proper input validation with parameterized queries or avoid eval usage entirely in DNS record processing functions.

Recommended fix High confidence

HestiaCP version 1.9.5

  1. 1. Back up your current HestiaCP installation and all associated data before proceeding with any changes.
  2. 2. Upgrade HestiaCP to version 1.9.5 or later. Run the official HestiaCP upgrade command: 'v-update-sys-hestia' or download the latest release from the official repository.
  3. 3. After upgrading, verify the installation completed successfully by checking the HestiaCP version with 'v-list-sys-hestia' or accessing the web interface.
  4. 4. Confirm that the patch containing commit a74babb739aa92e52b12d6ef52b6b9428ffbbb67 has been applied by reviewing the DNS-related functions in the source code, specifically is_dns_record_format_valid() and update_domain_zone().
  5. 5. As a precaution, review all user accounts and consider resetting credentials for low-privilege users who had access to the DNS management functionality.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control Panel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30007 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data