I really like the quality and service of Plesk. They focus on useful tools. There are no functions just to be cool or just to have a buzzword in advertisement. The quality is fine so far. But telling it is on purpose to install an update a day later then everyone else really annoys me. It looks...
I have 3 servers with Plesk and they all did the update to 6.2.2 this night between 2AM and 7AM. Plesk delayed the updates by around 20 hours compared to pages that do not use Plesk.
Seems all three issues are even worse than reported in my first post:
I have five test pages outside of Plesk with extremely low traffic. All got their automatic updates to 6.2.2. See the screenshot of the mail from 14 hours ago. But all Plesk sites are still on 6.2.1 and Plesk does not even...
https://core.trac.wordpress.org/ticket/57363#comment:4
Now I fond something. The Wordpress Dev says yeah the bug exists but simply use a trusted DNS, send some good hopes with your prayers and maybe nobody will be affected.
(Following this logic, no Wordpress page should use HTTPS as Wordpress'...
Sorry after reading again, I am not sure any more. They say: "as they need more time to work on backports." What I read was: The Wordpress Maintainers think the bug is fixed in Wordpress 6 but had to fix Wordpress 5, too.
I can't find an official statement from Wordpress or an independent proof...
Plesk is wrong. The vulnerability is fixed in 5.9.3 according to the authors of the bug report. WordPress Core - Unauthenticated Blind SSRF | Sonar
I get the message for a not existing WordPress UpdraftPlus PRO, too.
Hi!
All my Wordpress sites show these warnings at the moment. Sorry I can't switch Plesk to English. There are several issues with this.
My sites are in 6.2.1 but the current Core version is 6.2.2, not 6.2.1, Plesk does not provide the update.
The bug shown is fixed in 5.9.3 according to the...