Plesk vulnerabilities

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.

Improper privilege management in the XML-RPC API of Plesk before 18.0.80 allows an authenticated reseller to obtain an administrative session for the root user account.

Improper neutralization in the Plesk XML-RPC API allows a remote authenticated low-privileged user to perform SQL injection and read arbitrary data from the Plesk database, leading to full compromise of the panel.

An improper authorization vulnerability in the Plesk XML API allows an authenticated user to inject arbitrary configuration directives, resulting in arbitrary file write as root and full privilege escalation on the underlying server.

Plesk contains an XPath injection vulnerability in the APS Application Catalog search functionality, where user-supplied input is interpolated into XPath queries without proper sanitization. This allows an authenticated, low-privileged user to execute arbitrary operating system commands on the server, resulting in local privilege escalation.

Plesk 18.0 has Incorrect Access Control.

Plesk has a vulnerability involving improper symlink resolution before file access, allowing remote authenticated users to execute arbitrary code as root.

Plesk has a vulnerability involving improper neutralization of special elements, allowing remote authenticated users to disclose arbitrary local files and escalate privileges.

Plesk versions 18.0.79.7 and earlier, and 18.0.80 through 18.0.80.3, have an insecure direct object reference vulnerability, allowing remote authenticated users to read and modify other customers' databases.