CVE-2025-30008
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 · uneditedHestiaCP before 1.9.5 contains a stored cross-site scripting vulnerability that allows authenticated low-privilege users to inject arbitrary HTML by creating a DNS record with a double-quote followed by a script payload in the value field. The application fails to apply htmlspecialchars() encoding to the DNS record value field rendered into the data-sort-value HTML attribute in list_dns_rec.php, allowing the payload to execute in the browser of any user who views the DNS record list, including administrators.
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 confidenceHestiaCP before 1.9.5 has a stored XSS vulnerability in list_dns_rec.php where the DNS record value field is rendered into a data-sort-value HTML attribute without proper sanitization. Authenticated low-privilege users can inject malicious scripts via DNS record values containing a double-quote break-out and script payload, which executes when administrators or other users view the DNS record list.
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< 1.9.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check HestiaCP versionLog in as admin and navigate to the system information page or run 'v-list-sys-info' via CLI to view the installed HestiaCP versionAffected if The installed version is any version before 1.9.5 (e.g., 1.9.4, 1.9.3, etc.)
-
Locate the vulnerable scriptCheck for the presence of list_dns_rec.php in the web interface directory, typically found in /list/dns/ within the HestiaCP installationAffected if The file list_dns_rec.php exists on the system and the HestiaCP version is below 1.9.5
-
Verify DNS record management accessCheck if low-privilege or non-admin users have permissions to create or edit DNS records in the HestiaCP user management panelAffected if Low-privilege users have DNS record creation or editing permissions enabled
-
Inspect DNS records for injected scriptsReview existing DNS records in the control panel or query the DNS zone files/database for any records containing HTML tags, script elements, or double-quote characters that could indicate XSS payload attemptsAffected if Any DNS record value contains suspicious patterns such as <script>, javascript:, onerror=, or contains unescaped double-quote characters that break out of the data-sort-value attribute
The environment is affected if HestiaCP version is below 1.9.5 AND low-privilege users have access to manage DNS records, or if suspicious XSS payloads are already present in DNS record values.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.9.5
Upgrade to HestiaCP 1.9.5 or later, which applies htmlspecialchars() encoding to the DNS record value field in the data-sort-value attribute. As a workaround, restrict low-privilege user permissions until upgrade is completed.
1.9.5
- Upgrade HestiaCP to version 1.9.5 or later to resolve the stored XSS vulnerability
- After upgrading, verify that htmlspecialchars() encoding is properly applied to DNS record value fields in list_dns_rec.php
- Confirm that existing DNS records with potentially malicious payloads are reviewed and cleaned if necessary
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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