Wordfence version 7.10.5 released today

Hello all! We have a new release for Wordfence today, version 7.10.5. Please update as soon as you are able.

• Improvement: Updated the bundled GeoIP database
• Improvement: Added detection for Cloudflare reverse proxies blocking callbacks to the site
• Change: Files are no longer excluded from future scans if a previous scan stopped during their processing
• Fix: Added handling for the pending WordPress 6.4 change that removes $wpdb->use_mysqli
• Fix: The WAF MySQLi storage engine will now work correctly when either DB_COLLATE or DB_CHARSET are not defined
• Fix: Added additional error handling to Central calls to better handle request failures or conflicts
• Fix: Addressed a warning that would occur if a non-repo plugin update hook did not provide a last updated date
• Fix: Fixed an error in PHP 8 that could occur if the time correction offset was not numeric
• Fix: 2FA AJAX calls now use an absolute path rather than a full URL to avoid CORS issues on sites that do not canonicalize www and non-www requests
• Fix: Addressed a race condition where multiple concurrent hits on multisite could trigger overlapping role sync tasks
• Fix: Improved performance when viewing the user list on large multisites
• Fix: Fixed a UI bug where an invalid code on 2FA activation would leave the activate button disabled
• Fix: Reverted a change on error modals to bring back the additional close button for better accessibility

Thanks everyone for the great comments and suggestions. Send any of those you might have to [email protected] and someone will get back to you. Keep in mind, the feedback address is not a place to request support. Also, no support questions will be answered in this thread. Free support requests can be posted at https://www.ads-software.com/support/plugin/wordfence

Our Premium customers can open a ticket on the Licenses page in their account on Wordfence.com. Just click the red Get Help button to start the process.