Exploit Scanner · Security record
Is Exploit Scanner safe?
One known vulnerability affects the current version (1.5.2), and it has no fix yet.
Checked 2 days ago against the WPVulnerability database, for version 1.5.2.
How it’s looked after
- Last release
- Nov 28, 2017 (8 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 4.7.39 (current: 7.1)
- Active installs
- 8K+
4 known vulnerabilities
- 4 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20131
- 20151
- 20231
Every known vulnerability in Exploit Scanner
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · WPScan
Fixed in 1.3.4 · May 15, 2023 · Patchstack
Fixed in 1.3.4 · May 15, 2015 · Patchstack
Fixed in 1.3.4 · May 29, 2013 · Wordfence
Questions about Exploit Scanner’s security
Is Exploit Scanner safe to use?
Yes: 1 known vulnerability affects version 1.5.2, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Exploit Scanner have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.5.2, according to WPVulnerability’s database.
Is Exploit Scanner still maintained?
Its last release was 8 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Exploit Scanner compatible with the latest WordPress?
Exploit Scanner’s readme says it’s tested up to WordPress 4.7.39, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.