LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64639: Incorrect database cloning process in Plesk from 18.0.52 before 18.0.79.6 and 18.0.80.2 allows a low-privil...

Incorrect database cloning process in Plesk from 18.0.52 before 18.0.79.6 and 18.0.80.2 allows a low-privileged user (customer, reseller) to execute arbitrary code on behalf of the database server administrator.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in Plesk’s database-cloning process can let a customer or reseller run arbitrary code with the database server administrator’s authority. Successful abuse could compromise hosted databases and their confidentiality, integrity, and availability. The supplied record rates the issue critical.

Executive priority

Prioritize remediation immediately because successful exploitation could give a tenant database-administrator-level code execution and affect hosted data. Confirm all Plesk estates and managed hosting providers are patched. Although active exploitation is not established, the critical impact and low-privilege attack scenario justify urgent action.

Technical view

CVE-2026-64639 is a CWE-266 privilege-management flaw affecting Plesk releases from 18.0.52 before the vendor’s fixed releases 18.0.79.6 and 18.0.80.2. The vulnerable cloning workflow can execute attacker-controlled code under the database server administrator account. The supplied CVSS 4.0 score is 9.3.

Likely exposure

Exposure is likely where affected Plesk versions are installed and customer or reseller accounts can access database-cloning functionality. Internet-facing hosting environments and multi-tenant control panels warrant urgent review. The supplied sources do not identify particular operating systems, configurations, or databases as prerequisites.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation is described as possible by a low-privileged customer or reseller through database cloning. Treat credible tenant accounts as a meaningful threat boundary.

Researcher notes

The bundle describes exploitation by a low-privileged customer or reseller, while the supplied CVSS vector states PR:N. This inconsistency should be resolved against the authoritative CVE and vendor records. No exploit method, observed campaign, workaround, or forensic indicator is provided. Version interpretation should follow Plesk’s branch-specific advisory.

Mitigation direction

  • Update affected Plesk installations to 18.0.79.6, 18.0.80.2, or a later vendor-supported release.
  • Follow the linked Plesk advisory for branch-specific update guidance.
  • Restrict database-cloning access for customer and reseller accounts until updates are verified.
  • Review privileged database activity for unexpected code execution or changes.

Validation and detection

  • Inventory every Plesk instance and record its exact installed version.
  • Confirm each installation is 18.0.79.6, 18.0.80.2, or later, as applicable.
  • Identify customer and reseller accounts permitted to clone databases.
  • Review database administrator logs around cloning operations for anomalous processes or changes.
  • Verify updates succeeded and database-cloning operations still enforce intended privilege boundaries.
Prepared
Confidence
high
Sources
3

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.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-64639 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
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:Nhackerone

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-64639Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WebProsPlesk18.0.52, 18.0.80.0unaffected
Weakness

CWE details

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

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.