Wordfence Premium 8.0.4

Improvement: Added translation support for strings from login security plugin
Improvement: Added translator notes regarding word order and hidden text
Improvement: Added translation support for additional strings
Improvement: Prevented scans from failing if unreadable directories are encountered
Improvement: Added help link to IPv4 scan option
Improvement: Updated scan result text to clarify meaning of plugins removed from wordpress.org
Improvement: Made “Increased Attack Rate” emails actionable
Improvement: Updated GeoIP database
Improvement: Updated JavaScript libraries
Fix: Corrected IPv6 address expansion
Fix: Ensured long request payloads for malicious requests are recorded in live traffic
Fix: Prevented “commands out of sync” database error messages when the database connection has failed
Fix: Prevented rare JSON encoding issues from breaking free license registration
Fix: Prevented PHP notice from being logged when request parameter is missing
Fix: Prevented deprecation warning in PHP 8.1
Change: Moved detection for old TimThumb files to malware signature
Change: Moved translation file from .po to .pot
Change: Renamed “Macedonia” to “North Macedonia, Republic of”

Improvement: Added exception handling to prevent WAF errors from being fatal
Fix: Corrected error caused by method call on null in WAF
Change: Deprecated support for PHP 5.5 and 5.6, ended support for PHP 5.3 and 5.4
Change: Specified WAF version parameter when requesting firewall rules

Improvement: The vulnerability severity score (CVSS) is now shown with any vulnerability findings from the scanner
Improvement: Changed several links during initial setup to open in a new window/tab so it doesn’t interrupt installation
Change: Removed the non-https callback test to the Wordfence servers
Fix: Fixed an error on PHP 8 that could occur when checking for plugin updates and another plugin has a broken hook
Fix: Added a check for disabled functions when generating support diagnostics to avoid an error on PHP 8
Fix: Prevent double-clicking when activating 2FA to avoid an “already set up” error