Wordfence Security Vulnerabilities
The Wordfence Security WordPress plugin has 5 known security vulnerabilities. The most recent was disclosed on May 10, 2016. Check whether your site runs an affected version below.
View Wordfence Security on WordPress.orgSummary
Latest vulnerability disclosed on May 10, 2016.
Recommendation
WPSentry recommends installing with caution
Use Wordfence Security only with care. This plugin has a history of high-severity vulnerabilities — always run the latest version and monitor it for newly disclosed issues.
Is your site affected?
Run a free external scan to detect Wordfence Security and 35+ other WordPress security checks — no login or plugin required.
Known Wordfence Security vulnerabilities
- medium
Wordfence Security – Firewall & Malware Scan 6.1.1 - 6.1.6 - Reflected Cross-Site Scripting
Affected versions: <=6.1.6Disclosed May 10, 2016 - high
Wordfence Security <= 5.2.3 - Stored Cross-Site Scripting via HTTP_HOST
Affected versions: <=5.2.3Disclosed September 27, 2014 - high
Wordfence <= 5.2.3 - Stored Cross-Site Scripting via REQUEST_URI
Affected versions: <=5.2.3Disclosed September 14, 2014 - high
Wordfence <= 5.2.2 - Stored Cross-Site Scripting
Affected versions: <5.2.3Disclosed September 8, 2014 - high
Wordfence Security <= 3.8.1 - Stored Cross-Site Scripting
Affected versions: <=3.8.1Disclosed August 1, 2014
How to stay protected
Update promptly
Keep Wordfence Security on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.