Plesk 17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 17 | 17.8.11.95 | Apr 20, 2021 | EOL |
| 18.0.49 | 18.0.49.2 | Mar 12, 2023 | EOL |
| 18.0.50 | 18.0.50.2 | Apr 23, 2023 | EOL |
| 18.0.51 | 18.0.51.1 | Jun 6, 2023 | EOL |
| 18.0.52 | 18.0.52.3 | Jul 18, 2023 | EOL |
| 18.0.53 | 18.0.53.2 | Sep 4, 2023 | EOL |
| 18.0.54 | 18.0.54.4 | Oct 10, 2023 | EOL |
| 18.0.55 | 18.0.55.2 | Nov 21, 2023 | EOL |
When Plesk 17 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Plesk 17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.