LiveActive security incident?Get immediate response
CVE Record

CVE-2021-30070: An issue was discovered in HestiaCP before v1.3.5.

An issue was discovered in HestiaCP before v1.3.5. Attackers are able to arbitrarily install packages due to values taken from the pgk [] parameter in the update request being transmitted to the operating system's package manager.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

HestiaCP versions before 1.3.5 allowed attacker-supplied update parameters to reach the operating system package manager, enabling arbitrary package installation. For a hosting control panel, that can affect server integrity. Public sources do not provide CVSS, authentication requirements, or confirmed exploitation.

Executive priority

Treat this as a near-term remediation item for any HestiaCP-managed server. The business risk is unauthorized software installation on hosting infrastructure, but urgency should be calibrated because exploitation status and prerequisites are not documented in the provided sources.

Technical view

The CVE describes insufficient handling of the update request pkg[] parameter in HestiaCP before v1.3.5. Values from that parameter were transmitted to the OS package manager, allowing arbitrary package installation. Two upstream commits are cited, but the source bundle does not include detailed exploit prerequisites or impact scoring.

Likely exposure

Exposure is limited to organizations running HestiaCP before v1.3.5. The source bundle does not identify CPEs, deployment defaults, authentication state, or whether internet-facing panels are specifically required.

Exploitation context

CISA KEV status is false in the source bundle, and no cited source states active exploitation. The public description indicates attacker-controlled package selection through an update request, but does not provide safe details about required access or exploit maturity.

Researcher notes

Key gaps are missing CVSS, missing CWE, no CPEs, and unclear attacker prerequisites. Analysis should focus on the update request handling fixed by the two referenced HestiaCP commits and whether deployed instances expose the vulnerable workflow.

Mitigation direction

  • Upgrade HestiaCP to v1.3.5 or later.
  • Review the cited upstream commits for the exact fixed behavior.
  • Check HestiaCP vendor guidance for any additional hardening steps.
  • Limit administrative panel access to trusted users and networks where operationally possible.
  • Review package installation history for unexpected changes.

Validation and detection

  • Inventory all HestiaCP installations and record their versions.
  • Confirm no instance is running a version before 1.3.5.
  • Review package manager logs for unexpected package installations.
  • Review HestiaCP update activity around suspicious timestamps.
  • Validate remediation against the referenced upstream commits.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-30070 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.