Help Documentation

Wordfence plugin documentation and support
Suggestions:
If Your Site Is HackedTuning Wordfence Resource UsageV3: Accessing and Consuming the Vulnerability Data FeedAPI CallbacksVulnerability Management: Webhook NotificationsBasic Plugin SettingsAudit LogV1: Accessing and Consuming the Vulnerability Data FeedV2: Accessing and Consuming the Vulnerability Data FeedWordfence IntelligenceCompatibilityWordfence Intelligence Webhook NotificationsWordfence ResponseWordfence CareWordfence FreePlugin / Theme ConflictsUsing Wordfence Central TeamsSub-Processors ListMySQLi storage engineAccount and Billing HistoryUsing Central’s Settings pageLogin Security PluginLogin Security OptionsLegacy Two-Factor AuthenticationUsing Wordfence plugin options TemplatesUsing the Configuration pageViewing scan FindingsUsing the Dashboard pageSetting up two-factor authenticationConnecting your sites to Wordfence CentralWordfence Central ToolImport/ExportWordfence and GDPR – General Data Protection RegulationTroubleshootingTechnical DetailsWordfence 7Blocking TroubleshootingWordfence and LiteSpeedDiagnosticsWHOIS LookupBrute Force ProtectionStatisticsGlobal OptionsWordfence APIAlertsDashboardToolsRate LimitingChangelogScan TroubleshootingFirewall Optimization TroubleshootingScan ResultsConstantsTroubleshootingLicense KeyRemove or ResetSystem requirementsScan SchedulingCountry BlockingScan OptionsFirewall OptionsFirewall Learning ModeAdvanced information and configurationIncident Response ServicesTwo-Factor AuthenticationReal-Time Live TrafficScanBlockingWordfence PremiumOptimizing The FirewallWordfence Web Application Firewall (WAF)

Free Support

Support for users of the free version of the plugin is available on our WordPress.org support forum. The majority of requests receive an answer within a few days.
GO TO SUPPORT FORUMS

Access Upgraded Support Now

Our senior support engineers respond to Premium tickets within a few hours on average and have a direct line to our QA and development teams.
UPGRADE WORDFENCE

or log in here

Changelog

Historical information about previous Wordfence plugin versions.

= 8.2.2 – May 13, 2026 =

* Improvement: Better presentation of Live Traffic data on wide screens
* Improvement: Increased legibility of token fields
* Improvement: Reworked the pagination of the Blocking page for a better UX
* Improvement: Country blocking token field can now expand to show all entries
* Improvement: Performance improvements for the activity log and better pause behavior on window blur/focus
* Improvement: GeoIP database updated
* Change: Removed deprecated Central endpoint
* Fix: Addressed issue where the last activity log entry could repeatedly appear
* Fix: Using the embedded shortcode for the 2FA form now correctly enqueues core JavaScript dependencies
* Fix: Modals with content that overflows on smaller viewports can now be scrolled
* Fix: The changelog link in plugin upgrade scan issues now links correctly

= 8.2.1 – May 6, 2026 =

* Fix: Fixed issue with some i18n plugins/themes when a user has no 2FA recovery codes.
* Fix: Toggled options with additional help links now correctly open the link rather than toggling the option.
* Fix: Country Blocking editing fixed when there are multiple pages of block rules.
* Fix: Added better error handling to the initial Vue data load.
* Fix: Handled error when logging in using legacy 2FA with separate prompts enabled.

= 8.2.0 – April 29, 2026 =

* Improvement: Migrated all deprecated JavaScript libraries in use to a Vue-based infrastructure.
* Improvement: GeoIP database update.
* Improvement: Better coverage of `aria-` accessibility attributes.
* Improvement: Added `translators` comments to translatable strings where previously missing.
* Fix: WordPress 7.0 compatibility fixes.
* Note: Legacy two factor authentication using SMS-based codes will be discontinued around July 1, 2026. Sites using this functionality should migrate users to the TOTP-based two factor authentication on the Login Security page of the plugin.

= 8.1.4 – December 20, 2025 =

* Fix: Fixed an issue with `inet_pton` introduced by a recent patch to PHP 8.1+ that could cause a fatal error if a malformed IP address was passed to the call.

= 8.1.3 – December 3, 2025 =

* Improvement: Updated the bundled geoip database.
* Note: Verified compatibility with WordPress 6.9

To view a complete changelog, visit this link here

This website uses cookies, pixels, and similar technologies (collectively “Cookies”) to improve your browsing experience. By clicking “Accept All”, you agree to the storing of Cookies on your device and that we may share, track, store, and analyze your interactions with the website to enhance site navigation, analyze site usage, and assist in our marketing efforts. For more information on our use of cookies please review our Cookie Policy.