VulnerabilityPublished 10 Jul 2026Updated 8 Nov 2026

CVE-2025-30008: hestiacp · Cross-site Scripting

Affects hestiacpSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.9.5 when convenient.

Data as of 8 Nov 2026, 14:20 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	5.1
CNA (VulnCheck)	CVSS 3.1	4.6

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-07-10.

Patch

Available – fixed in 1.9.5

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade hestiacp to 1.9.5.

Affected software

Product	Affected	Fixed in
hestiacphestiacp	Affected <1.9.5	Fixed in–
GitHubhestiacp`pkg:github/hestiacp`Other threats	Affected <1.9.5	Fixed in 1.9.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade HestiaCP to version 1.9.5 or later, where this vulnerability is fixed. The fix involves proper encoding of the DNS record value field to prevent script injection. Until upgraded, restrict access to the DNS record management interface to trusted users only.

Description

HestiaCP versions before 1.9.5 contain a stored cross-site scripting (XSS) vulnerability. Authenticated low-privilege users can inject arbitrary HTML by creating a DNS record with a crafted value containing a double-quote and script payload. The vulnerability arises because the application does not properly encode the DNS record value when rendering it into an HTML attribute, allowing script execution in the browsers of users who view the DNS record list, including administrators. This issue is fixed in version 1.9.5.

Impact

An authenticated low-privilege user can inject arbitrary HTML/JavaScript that executes in the browsers of users who view the DNS record list page, including administrators. This can lead to session hijacking, unauthorized actions, or other attacks leveraging the victim's browser context. However, exploitation requires authentication and user interaction (viewing the DNS record list). No known exploits in the wild have been reported.

Summary

CVE-2025-30008 is a stored cross-site scripting vulnerability in HestiaCP prior to version 1.9.5. The flaw occurs due to improper neutralization of input during web page generation: the DNS record value field is not passed through htmlspecialchars() encoding before being embedded in the data-sort-value HTML attribute in list_dns_rec.php. This allows an authenticated user with low privileges to inject a payload that executes in the context of any user viewing the DNS record list, potentially including administrators. The vulnerability has a CVSS 4.0 base score of 5.1, indicating medium severity. The issue is resolved in HestiaCP 1.9.5.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Nov 2026, 14:20 UTC

Technical details

References

Community reviews

Related threats