• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Contradictory Plugin Listings - BackupBuddy 8.7.5

Peter Downes

Basic Pleskian
Server operating system version
CloudLinux 7.9 (Boris Yegorov)
Plesk version and microupdate number
Plesk Obsidian v18.0.46_build1800220905.16 os_CentOS 7
Hi Community

Plesk WordPress Toolkit is showing my sites are using BackupBuddy 8.7.5 under Plugins
https://~/modules/wp-toolkit/index.php/index/plugins

And has a Vulnerable tooltip warning which reads 'WordPress Backup Buddy plugin 8.5.8.0 - 8.7.4.1 - Unauthenticated Path Traversal / Arbitrary File Download vulnerability '

Why show a Vulnerable tooltip warning for a version of the plugin that is not vulnerable according to Patchstack?

Just confused.
 
Hello! The bug in WordPress Toolkit is confirmed: EXTWPTOOLK-9721. This is because "fixed in" version of the vulnerability contains build number 0 and comparison doesn`t work correctly. In the other words this means that plugin version 8.7.5 and vulnerability "fixed in" version 8.7.5.0 is not he same :(
 
Hello! The bug in WordPress Toolkit is confirmed: EXTWPTOOLK-9721. This is because "fixed in" version of the vulnerability contains build number 0 and comparison doesn`t work correctly. In the other words this means that plugin version 8.7.5 and vulnerability "fixed in" version 8.7.5.0 is not he same :(
Thank you - that makes sense (tho' I couldn't load the link).
 
Back
Top