The upgrade of the plugin will then happen as part of the Moodle upgrade process.
If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.
A likely cause is the memory limit in default php installations (usually 8 MB). If the page just hangs loading during some time (like 30 seconds) doing a specific action, and then it results in a blank page or HTTP 500 error, the problem is a timeout connecting to some server.
This may be the database server, or if it happens doing a specific action, the mail server (if you have configured email settings).
There are three areas that should be backed up before any upgrade: See Site backup for more specific information.
If you have Automatic updates deployment enabled, you will be able to update installed plugins automatically during the upgrade.
That will break every contrib that depends on libraries, every time.
The way to avoid that is to either update core with Composer as well, or to not replace vendor/, but run "composer drupal-update" after the core update.
Just make sure you check for available updates (via the button for it) at the Plugins check screen.
If you are updating plugins manually, it is a good moment now to check in the Moodle Plugins directory whether there is a 2.9 version available for any plugins (including themes) that you have previously installed on your site. In the next step, you will copy it to the appropriate location in your Moodle code (see Installing plugins).
I hope we were successful in helping you resolve your issue with Wordfence!
Since we have not heard back from you in the past 2 weeks I will now be marking this support thread as resolved.
This issue is caused by Plesk bug #PPPM-6104 and will be fixed in future product updates.