← All articles

Wordfence 9.1.1 Updates Security Rules and Login Logs

Wordfence 9.1.1 Updates Security Rules and Login Logs

Wordfence 9.1.1 is now available after Wordfence 9.1.0 added faster firewall updates, sharper request inspection and broader logging of failed WordPress logins. The follow-up release, issued on November 10, 2026, updates the bundled list of trusted root certificates, called cacert.pem, which Wordfence uses to verify secure connections. It adds no features and changes no settings. The other changes described here remain part of 9.1.0, released on November 9, 2026.

The larger update adds a Wordfence Security News Widget to both the WordPress dashboard and the Wordfence dashboard. It displays the latest posts from the Wordfence blog, including security alerts and research, so administrators do not have to visit the blog, open the WordPress Security Newsletter or follow social media to find them. Links to Wordfence news, the blog, newsletter and Security Learning Center appear at the bottom of the widget. The widget is free for all Wordfence users, regardless of licence.

After updating to 9.1.0, the widget is enabled in both dashboards. Administrators can go to Wordfence, Dashboard, Global Options, then expand Wordfence Security News. From there, they can enable or disable it separately for each dashboard and choose Rich mode, which includes summaries, or Compact mode, which shows headlines only.

The firewall, a security filter that examines incoming website requests, now checks for rule updates more often. Wordfence says this helps reduce the time between a threat being identified and a new rule reaching a site. Premium sites receive new rules in real time, while Free sites receive them after the standard 30-day delay. The more frequent checks apply to both groups, but they do not remove that difference in delivery speed.

Request parsing, meaning the way security software interprets information sent to a website, has also been changed. Attackers can hide harmful input in malformed or deeply nested requests and rely on a firewall interpreting the data differently from WordPress. Wordfence says the updated firewall handles these requests more like WordPress does. The changes include improved detection of malformed SQL injection attempts, better handling of deeply nested request arrays, and matching the firewall’s inspection of form request bodies to WordPress method overrides. A method override allows some requests to act as though they used a different HTTP method.

The malware scanner also handles uploaded files better. These detection changes are available to all Wordfence users and do not require a setting to be enabled.

Live Traffic now records failed authentication attempts made through application passwords and the REST API, two login routes that do not use wp-login.php. The REST API is a way for software to communicate with WordPress. To find these entries, administrators can open Wordfence, Tools, Live Traffic, select Show Advanced Filters, choose Add Filter, and then select Authentication. A failed entry shows who tried to sign in, which user account was targeted and why the attempt failed. Administrators can also block the IP address or look it up.

The update adds control over WAF attack alerts. A web application firewall, or WAF, is a filter designed to identify and block harmful web requests. Site owners can now choose how many attacks must occur during a specified counting window before Wordfence sends an alert. The settings are under Wordfence, Dashboard, Global Options, Email Alert Preferences. The fields are Number of attacks before sending an alert and Attack counting window (minutes). Raising the threshold reduces alert sensitivity and can limit noise on busy sites, while lowering it can report smaller bursts of activity.

Wordfence 9.1.0 also includes PHP 8.6 compatibility fixes and reliability improvements for unusual hosting environments, including hosts that disable ini_set and servers that send PHP diagnostic output. Other changes improve attack-data synchronisation, validation of cached real-time IP blocklist data, two-factor authentication recovery-code validation and reCAPTCHA key validation when keys are saved. The release also updates the GeoIP database.

Further fixes adjust audit-log request data and limits, use the site’s timezone and UTC offset in the scan activity log, and handle canceled requests more reliably. Passkey availability checks are better protected when database setup is incomplete or broken. Live Traffic descriptions for requests without a referrer were corrected, and the satisfaction survey notice received layout and dismissal fixes.

No settings need to be changed after updating. The optional choices concern the news widget’s visibility and layout, plus the WAF alert threshold and counting window. Automatic plugin updates install the update when enabled. Manual updates are available through Dashboard, Updates, or Plugins in WordPress. Site management tools can update several sites in bulk, while Wordfence Central shows the security status of connected sites.

For readers who want their WordPress environment handled as a whole, AEU Hosting provides managed WordPress hosting, secured end to end. Updating Wordfence remains a site administration task, and the release does not remove the need to keep WordPress and its plugins maintained.

The practical priority is to update to Wordfence 9.1.1, then review the new alert and dashboard options so the information shown matches the way the site is managed.

Also available in: DeutschItalianoShqip