I first felt the same, but now I'd actually prefer that Plesk does not publish what exactly was improved. Because, if they did, they'd foremost give hackers a hint how to attack. Maybe a compromise, first publish the message that we must absolutely update, then wait another two to four weeks, then explain why the update was important.
@Bitpalast
As for me, the evolution of opinions is - exactly - the other way around.
At first, I would have agreed with you : careful release of vulnerability information would have been preferred.
Now, this has completely changed ....... and I prefer to have full disclosure upfront.
There are three reasons for this change :
1 - some vulnerabilities are quite easy to mitigate or annihilate completely : information upfront allows Plesk admins to take immediate action
2 - Plesk updates are not released instantly and/or can be buggy (with some of them even increasing the vulnerability that was intended to be patched) and some Plesk updates do not patch all known vulnerabilities (which is normal) : information upfront allows Plesk admins to take appropriate action after updates
3 - the attack surface and the number of vulnerabilities will increase with the continuous release of more advanced AI : information upfront (to humans, Plesk admins) is stating "the obvious" that has already been disclosed (by humans, security researchers and hackers alike) as more or less "public" information that has been "learned" (by AI) and that still has to be "learned" by most Plesk admins (humans, needing information upfront to know something)
However, the main reason for this change and evolution towards "full disclosure upfront is required" is totally different from the 3 aforementioned reasons.
In essence, people are inclined to become passive and to wait for Plesk updates ........ if those updates "promise" to resolve issues.
The difference between "active" and "passive" is the time to react upon a certain situation and this time is positive, not zero.
The time to react upon a certain situation, if and when relying on Plesk updates, is exactly equal to SUM of the (given) time to develop the Plesk update, still to be augmented with the (variable) time to implement the Plesk update - which time of implementation can vary across Plesk admins.
The time to react upon a certain situation, if and when relying on "upfront information", can - by definition - be shorter and - probably - will be shorter.
In fact, the time always starts at the moment that the aforementioned "certain situation" is known.
In the case of relying on Plesk updates, there is the starting time (the moment where the situation is known), followed by the (given) time to develop Plesk, again followed by a (variable) time to implement the Plesk update.
In the case of relying on upfront information, there is the starting time (again the moment where the situation is known), followed by an opportunity to patch and/or mitigate the issue caused by the situation in question, hence providing time to safely wait for the Plesk update.
The aforementioned opportunity is real and valuable, since in most cases, mitigation or annihilation of specific situations can be fast.
Consider an issue that simply requires a kernel update ........ no solution in Plesk updates, but solutions are to be found in kernel updates (which are fast).
Consider an issue that simply requires one line of config code or an update of PHP ......... simply update PHP or adjust the config.
In short, it is highly valuable and desirable to reduce the time to react ......... and that can only be done when "information upfront" is provided.
Kind regards...
PS I do agree with you that, at least for some rare scenario's, full disclosure of information should never be considered. Nevertheless, these scenario's are really rare and then still it is valuable and desirable to share parts of the relevant information with respect to symptoms (hence not causes).