Quick answers
- Is CVE-2026-64639 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64639 being exploited in the wild.
- How severe is CVE-2026-64639?
- Informational severity, published 12 August 2026.
- Which products and versions are affected?
- Plesk 18.0.52 before 18.0.79.6 and 18.0.80.2.
- Is there a fix for CVE-2026-64639?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-64639 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-64639?
- Check whether you run Plesk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An incorrect implementation of the database cloning process in Plesk allows privilege escalation from low-privileged users (customer, reseller roles) to database server administrator level. The vulnerability exists in versions 18.0.52 through 18.0.79.6 and 18.0.80.2. By exploiting the cloning mechanism, an attacker can execute arbitrary code with database administrator privileges. The vulnerability requires authenticated access (user must have customer or reseller account on the Plesk instance). Patches are available in versions 18.0.79.6 and later.
Affected products
- Plesk Plesk 18.0.52 before 18.0.79.6 and 18.0.80.2
Timeline
- 2026-08-12: disclosed