• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

re: Plesk installs php 4.x - which is vulnerable?

J

JVRudnick

Guest
Hello plesk support and users...

I just got a new ded server here at ThePlanet, and I ran a Vulnerabilty Report right off the bat - and found that I have more'n 8 issues all with the version of php that was installed by Plesk 8.2.

They all begin with --
Vulnerability pcsync-https (8443/tcp)
Synopsis : The remote web server uses a version of PHP that is affected by multiple flaws.
Description : According to its banner, the version of PHP installed on the remote host is older than 5.2.6.

What I then asked TP support was why did they install, via my purchased Plesk 8.2 CP, vulnerabilities...and I got the usual run-around that they install only the most stable version...which is something like php 4.x...and it was Plesk's fault as they supplied the CP installer...

Can someone here offer...who's to blame here? Why would Plesk supply a version of php that is vulnerable - and why would ThePlanet not offer support on same....

Help here someone?

???

Jim
 
so...I'm the only guy who's ever run into this vulnerability?

or .... what maybe?

Jim
 
Same problem on 8.6.0.5

I'm having the same problem with PHP4 reporting vulnerabilities.
Did you ever solve this?
 
Back
Top