• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Critical Security Patch - Plesk 10.3.1

S

ScottT

Guest
Hello,

The critical security patch notification released 2/9/2012 suggests updating to Plesk 10.3.1 MicroUpdate #6 or later to resolve the vulnerability. My version of Plesk does not list MicroUpdate number. Instead Plesk gives this version: psa v10.3.1_build20110630.16. Is my version of Plesk vulnerable? Where do I find MicroUpdate number in Plesk 10.3.1? Thank you.
 
Last edited by a moderator:
Hmmm, I'd like to know the answer to this too. I'd also like to know, if this is only a risk to Plesk Panel if access to the the control panel is publicly available.
 
These instruction are for linux/unix. How do I find microupdate# in Windows?
 
My server does not have a PleskInstaller directory. I located microupdates.xml in another directory. Here are the contents:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<patches>
<product id="panel" version="10.3.1">
<patch version="10" timestamp="" />
</product>
</patches>


So, it appears I have MU #10 and my server is not vulnerable. Thanks for your help.
 
Last edited by a moderator:
Back
Top