• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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