Plugin Reviews

Exploit Scanner

Search the files and database of your WordPress install for signs that may indicate that it has fallen victim to malicious hackers.

6 reviews
Average Rating
3.2 out of 5 stars
You are currently viewing the reviews that provided a rating of 1 star. Click here to see all reviews.
Error occurred during scan
By , for WP 4.1.1

No error message besides the 'Error occurred' message. This is clearly broken, at least for WP multisites.

doesn't work for me
By , for WP 4.0.1

I get the following message:

"hashes-4.0.1.php missing
The file containing hashes of all WordPress core files appears to be missing; modified core files will no longer be detected and a lot more suspicious strings will be detected"

Then it lists 553 problems which is far too much.

Anyone know how to get it working?

DidnĀ“t work
By ,

Kept not finishing search and giving error message. UNINSTALL!

"hashes-3.x.php missing"
By , for WP 3.8

Every time I update WordPress, Exploit Scanner loses its hashes file and marks everything as compromised. The fact that you have to manually generate a replacement hashes file - there is no way through the GUI - means that it is of limited use to anyone bar expert users. And even then, its not guaranteed to work.

The developers don't seem to be keeping up pace with WordPress core development - the Plugin page lists 3.5.2 as latest supported version, whereas 3.8 is most up to date WP version as of writing.

An error occurred. Please try again later.
By , for WP 3.7.1

I haven't gotten it to work once yet. I've increased the memory it requires and set it to the Upper file size limit to 50k and number of files per batch to 100. It still times out or otherwise errors. Maybe it works, maybe it doesn't, but I'm not changing system-wide settings (that make my system more vulnerable) to get a scanner to work.

Error when running on site in network
By , for WP 3.5.1

We have a half-dozen blogs running on one WordPress installation. I installed this plugin and then attempted (1) Network activate, then run from different individual blog dashboards; and (2) Network deactivate, go to individual blog dashboard, activate, run from individual blog dashboard. Either way, I get a long error starting with:

{"status":"error","message":"$this->files was not an array","data":{"start":1000,"files":"s:102453

Screen shot

You must log in to submit a review. You can also log in or register using the form near the top of this page.