• 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.

Question ETA for Roundcube 1.6.20? (20 security fixes)

Cmdr

New Pleskian
Server operating system version
Ubuntu 24.04.5 LTS
Plesk version and microupdate number
18.0.81 #4
Hello,

Roundcube released a security update on October 19th. Version 1.6.20 and 1.7.5.


With everything going on with PHP and security vulnerabilities right now, I wanted to ask if there’s an ETA for when Plesk will update to this version.

Thanks!

Kind regards
 
Updating RoundCube to 1.6.20/1.7.5 is already in our team processing queue. The update will likely be introduced either along with Obsidian 18.0.83 or with one of the minor updates of 18.0.82. I cannot confirm when exactly for sure. Once there are more details I will follow up. Thank you for your patience in the meantime.
 
@Cmdr / @King555 As per the post by @Sebahat.hadzhi above, Plesk will, after fully testing, provide what you're looking for. That's the best / easiest option.

FWIW We didn't want to wait :D and because unlike Plesk, who have to ensure legacy support for users before releasing upgrades, new configs etc, we are able to focus purely on our own servers. So since Roundcube 1.7.4, we've run Roundcube on PHP 8.5.* ourselves, outside of Plesk. It's still fully interfaced with Plesk (e.g. all links from within the GUI Plesk Panel operate as though it were a Plesk managed Roundcube package, but it's invisible in the GUI **:8443/admin/pum/list and/or the **:8447/installer/add_components.html list. Opting for self-management means adopting responsibilty for Roundcube upgrades as well as the initial custom install. Upgrades take a bit longer than if it were a Plesk managed upgrade, due to the config required to ensure it always seeemlessly interfaces with Plesk. We're fine with the extra work & responsibility, but others may not be. Example of the Roundcube 1.7.4 > 1.7.5 post upgrade final checks:

Bash:
:~# echo "===== LIVE VERSION ====="
/opt/plesk/php/8.5/bin/php -r \
'include "/opt/roundcube/current/program/include/iniset.php"; echo RCMAIL_VERSION, PHP_EOL;'

echo
echo "===== LIVE TARGET ====="
readlink -f /opt/roundcube/current

echo
echo "===== LIVE HEALTHCHECK ====="
cd /opt/roundcube/current
/opt/plesk/php/8.5/bin/php bin/healthcheck.sh
printf 'healthcheck exit code: %s\n' "$?"

===== LIVE VERSION =====
1.7.5

===== LIVE TARGET =====
/opt/roundcube/releases/1.7.5

===== LIVE HEALTHCHECK =====
DB: OK
IMAP: OK (ssl://localhost:993)
SMTP: OK (ssl://localhost:465)
Managesieve: OK (tls://localhost:4190)
healthcheck exit code: 0
:/#
 
Back
Top