Wordfence vulnerability history, with firewall, scan, two-factor and alert settings to read
Match the installed Wordfence version against each record's affected range and patched versions field.
Then write down what no version number shows: firewall status and protection level, the scan schedule, two-factor roles and alert addresses.
On this page
Wordfence vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 12 records for Wordfence. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 7.6.1
Worked out from data retrieved on .
Every affected range listed in this source for Wordfence ends before version 7.6.1.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Wordfence Security - Firewall & Malware Scan <= 7.6.0 - Authenticated (Admin+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2022-3144
Affected versions- All versions up to and including 7.6.0
Patched versions: 7.6.1
Update to at least version 7.6.1.
Wordfence Security - Firewall & Malware Scan <= 7.1.13 - Reflected Cross-Site Scripting and Information Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.7)
Affected versions- All versions before 7.1.14
Patched versions: 7.1.14
Update to at least version 7.1.14.
Wordfence Security - Firewall & Malware Scan 6.1.1 - 6.1.6 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
Affected versions- From version 6.1.1 up to and including 6.1.6
Patched versions: 6.1.7
Update to at least version 6.1.7.
Wordfence <= 5.1.4 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2014-4932
Affected versions- All versions before 5.1.5
Patched versions: 5.1.5
Update to at least version 5.1.5.
Wordfence Security <= 5.2.3 - Stored Cross-Site Scripting via HTTP_HOST
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
Affected versions- All versions up to and including 5.2.3
Patched versions: 5.2.4
Update to at least version 5.2.4.
Show 7 older recordsHide the older records
Wordfence <= 5.2.3 - Multiple Protection Mechanism Bypasses
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- All versions before 5.2.4
Patched versions: 5.2.4
Update to at least version 5.2.4.
Wordfence <= 5.2.3 - Stored Cross-Site Scripting via REQUEST_URI
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
Affected versions- All versions up to and including 5.2.3
Patched versions: 5.2.4
Update to at least version 5.2.4.
Wordfence <= 5.2.2 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
Affected versions- All versions before 5.2.3
Patched versions: 5.2.3
Update to at least version 5.2.3.
Wordfence Security <= 3.8.1 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
Affected versions- All versions up to and including 3.8.1
Patched versions: 3.8.3
Update to at least version 3.8.3.
Wordfence Security - Firewall & Malware Scan <= 5.1.3 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2014-4664
Affected versions- All versions up to and including 5.1.3
Patched versions: 5.1.4
Update to at least version 5.1.4.
Wordfence Security - Firewall & Malware Scan <= 3.3.6 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- All versions up to and including 3.3.6
Patched versions: 3.3.7
Update to at least version 3.3.7.
Wordfence < 3.3.7 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
Affected versions- All versions before 3.3.7
Patched versions: 3.3.7
Update to at least version 3.3.7.
Check Wordfence on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Wordfence adds to a site, and who reaches its screens
The records on this page are those the source data files under the slug wordfence.
The plugin's WordPress.org listing says Wordfence Security includes an endpoint firewall, malware scanner, robust login security features, live traffic views, and more. Each takes something in: by the listing, the firewall identifies and blocks malicious traffic, Live Traffic monitors visits, including origin and IP address, and the scan reads file contents, posts and comments.
Who reaches its screens is the other question. The listing's multisite steps say that once network activated, Wordfence appears on the Network Admin menu and not on any individual site's menu. CVE-2022-3144 has a title that carries the access wording Authenticated (Admin+).
WordPress's documentation says an Administrator has access to all administration features within a single site. As this page's own step, list who holds that role from the Role column of the Users screen.
Reading Wordfence vulnerabilities by their fields, not their titles
Titles in the history name the plugin more than one way, including Wordfence, Wordfence Security and Wordfence Security - Firewall & Malware Scan, and Cross-Site Scripting is wording that recurs.
Whichever name a title uses, the comparison is between the installed version and that record's affected range and patched versions field.
- CVE-2022-3144, whose title ends Authenticated (Admin+) Stored Cross-Site Scripting. Affected: all versions up to and including 7.6.0. Patched: 7.6.1.
- CVE-2014-4932, titled Wordfence <= 5.1.4 - Reflected Cross-Site Scripting. Affected: all versions before 5.1.5. Patched: 5.1.5.
- CVE-2014-4664, whose title ends <= 5.1.3 - Cross-Site Scripting. Affected: all versions up to and including 5.1.3. Patched: 5.1.4.
- A record with no CVE id, whose title ends 6.1.1 - 6.1.6 - Reflected Cross-Site Scripting. Affected: from version 6.1.1 up to and including 6.1.6. Patched: 6.1.7.
- A record with no CVE id, titled Wordfence Security <= 3.8.1 - Stored Cross-Site Scripting. Affected: all versions up to and including 3.8.1. Patched: 3.8.3.
Overlapping ranges, a gap and the changelog
A patched version answers its own record, not the whole history: CVE-2014-4664 lists 5.1.4 as patched, and 5.1.4 falls inside the range of CVE-2014-4932, all versions before 5.1.5.
The record whose title carries <= 3.8.1 has a range that ends there and a patched versions field that gives 3.8.3. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
The changelog on the plugin's WordPress.org listing has, under 7.6.1, the line Fix: Prevented XSS that would have required admin privileges to exploit (CVE-2022-3144). Other entries there use the word Hardened for changes to the 2FA flow, and a change the changelog describes may have no record on this page, so read it before relying on the update guidance at the top of the history.
Carrying out the Wordfence checks without changing a setting
Each step reads a screen and writes something down.
Wordfence's text includes Start New Scan, Repair All Repairable Files, Delete All Deletable Files and Save Changes, and the listing says a repair overwrites changed files with a pristine, original version. Press nothing that carries those labels.
The WordPress Plugins screen includes each plugin's version number in its Description column, and the plugin's text gives its plugin name as Wordfence Security. Write down the version on that row and what its Automatic update column shows.
The plugin has an auto-update option as well. Its text says that from the dashboard you can find the Global Options for Wordfence such as alerts, automatic updates, and managing your site's Premium License, and the option is labelled Update Wordfence automatically when a new version is released? Note it, and what License Status shows.
The template for the plugin's firewall page has a link titled All Firewall Options, with the line Manage global and advanced firewall options. Look there for the labels Web Application Firewall Status and Protection Level. The plugin's text includes the wordings Enabled and Protecting, Learning Mode and Disabled, and Basic WordPress Protection and Extended Protection.
Write down the wording each setting shows and any date beside Learning Mode Until. The text says that when you first install the Wordfence Web Application Firewall, it will be in learning mode.
Then copy the exceptions. The text describes a table of URLs and parameters that will not be tested by the firewall, typically added while the firewall is in Learning Mode or by an admin who identifies a false positive. Look for it, and for the list labelled Allowlisted IP addresses that bypass all rules, and copy both in full.
The template for the plugin's Scan page has a link titled Scan Options and Scheduling, with the line Manage scan options including scheduling. Look for the heading Scan Scheduling, the option labelled Schedule Wordfence Scans and a choice the text words as Let Wordfence choose when to scan my site (recommended), beside a second choice for setting the schedule yourself. The listing's FAQ says Premium users can schedule scans for specific times and a higher frequency.
Write down the option, the choice, any days and hours shown, the Scan Type, and a line that begins Next scan in or reads No scan is scheduled.
A note in the listing's changelog puts the TOTP-based two factor authentication on the Login Security page of the plugin. Look on that page for 2FA Roles, where the text says to choose whether 2FA is required, optional, or not allowed for each role. Write down each role's value and what User Summary shows for Total Users and 2FA Active.
The Users screen has filter links for each role: open Administrator and list the accounts. The plugin's text includes the label 2FA Status. Wherever a screen shows it, note each account's entry. WordPress's brute-force guidance advises two-factor authentication for all administrators and privileged users. This page's own step is to compare the accounts against that list.
Copy in full the settings labelled Allowlisted IP addresses that bypass 2FA, passkey requirements, and reCAPTCHA and Require 2FA for XML-RPC call authentication.
The listing's FAQ says Wordfence sends security alerts via email to a list of email addresses you configure once it is installed, and the plugin's text says where alerts are sent can be changed in Global Options. Look there for the setting labelled Where to email alerts.
Write down every address and who reads it, then which entries under Email Alert Preferences are on, such as Email me if Wordfence is deactivated and Email me if the Wordfence Web Application Firewall is turned off.
Two more things bear on who receives alerts. The plugin's text includes a prompt to enter an email address to unsubscribe from alerts, which it says sends a confirmation link if the address exists on the alert email list. Ask each recipient whether alerts still arrive.
And under the heading Wordfence Central, the listing says highly configurable alerts can be delivered via email, SMS or Slack: look for Wordfence Central Status, note what it shows and ask who holds that account.
Wordfence security settings a version match cannot show
A version inside an affected range shows that a known record covers that copy of Wordfence.
It does not show whether anyone used the flaw, or anything the five checks read. It says nothing either about the firewall rules and malware signatures, which the listing says arrive via the Threat Defense Feed, in real time on Premium and delayed by 30 days on the free version.
Nor does it cover what sits beside the plugin folder: the plugin's text names a wordfence-waf.php file in the root of the WordPress installation, an auto_prepend_file setting in .htaccess and .user.ini, and a /wp-content/wflogs directory.
A WordPress security audit tests the login path the 2FA Roles setting sits on. It confirms that two-factor covers every administrator and editor rather than only the person who installed the plugin, and tests whether the two-factor and lockout controls on the login form also apply to requests signed with an application password.
Frequently asked questions
Each record carries its own range. CVE-2014-4932 covers all versions before 5.1.5 and lists 5.1.5 as patched, while another record covers only from version 6.1.1 up to and including 6.1.6. Check the installed version against every affected range in the history, then read the update guidance at the top of the history.
Read the version on the Wordfence Security row of the Plugins screen and set it beside the update guidance at the top of the history. WordPress displays an update notice there when a plugin hosted in its directory has a newer version. Wordfence's own text includes a message for sites on the LiteSpeed web server that begins To preserve the integrity of your website we are not running Wordfence auto-update. On LiteSpeed, go by the installed version, not the auto-update option.
The records here are those the source data files under the slug wordfence. Being filed there does not settle whether a record applies to a paid plan or to a sister plugin. The plugin's text says the standard installation includes free features that can be upgraded via a Premium license key, so write down License Status beside the version. It also says the Wordfence Login Security plugin contains a subset of the functionality found in the full Wordfence plugin, and a changelog line on the listing calls that plugin standalone: where a site has both, write down both versions.
Use one for the version comparison, and read its settings with care. Wordfence's text includes the message The Wordfence license you're using does not match this site's address. Premium features are disabled. Another notice says the site is linked to Wordfence Central under a different site URL, which it says is generally caused by duplicating the database from one site to another, such as from a production site to staging, and it recommends disconnecting this site only. Leave that to the site owner, press nothing, and read the same settings on the live site as well.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 3 of the 12 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Wordfence Security - Firewall & Malware Scan <= 7.6.0 - Authenticated (Admin+) Stored Cross-Site Scripting (CVE-2022-3144)
- Wordfence Security - Firewall & Malware Scan <= 7.1.13 - Reflected Cross-Site Scripting and Information Disclosure
- Wordfence Security - Firewall & Malware Scan 6.1.1 - 6.1.6 - Reflected Cross-Site Scripting
- Wordfence <= 5.1.4 - Reflected Cross-Site Scripting (CVE-2014-4932)
- Wordfence Security <= 5.2.3 - Stored Cross-Site Scripting via HTTP_HOST
- Wordfence <= 5.2.3 - Multiple Protection Mechanism Bypasses
- Wordfence <= 5.2.3 - Stored Cross-Site Scripting via REQUEST_URI
- Wordfence <= 5.2.2 - Stored Cross-Site Scripting
- Wordfence Security <= 3.8.1 - Stored Cross-Site Scripting
- Wordfence Security - Firewall & Malware Scan <= 5.1.3 - Cross-Site Scripting (CVE-2014-4664)
- Wordfence Security - Firewall & Malware Scan <= 3.3.6 - Stored Cross-Site Scripting
- Wordfence < 3.3.7 - Reflected Cross-Site Scripting