Plugin Security Checker
This plugin will warn you if you're using or installing a knew as vulnerable extension or removed from official repository, a security must have …
Maintenance 22/1004401d since update
Active installs
600
Downloads
11,313
Reviews
8
Age
14.9y
Tagssecurityprotectionsecureexploitguard
Plugin info
Total downloads: 11,313
Active installs: 600
Total reviews: 8
Average rating: 4.9
Support threads opened: 0
Support threads resolved: 0 (0%)
Available in: 1 language(s)
Contributors: 4
Last updated: 12/13/2013 (4401 days ago)
Added to WordPress: 2/24/2011 (14 years old)
Minimum WordPress version: 3.1
Tested up to WordPress version: 3.6.1
Minimum PHP version: f
Maintenance & Compatibility
Maintenance score
Possibly abandoned • Last updated 4401 days ago • 8 reviews
22/100
Is Plugin Security Checker abandoned?
Possibly abandoned (last update 4401 days ago).
Compatibility
Requires WordPress: 3.1
Tested up to: 3.6.1
Requires PHP: f
Languages
Similar & Alternatives
Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.
WP Email Guard
Rating 0.0/5 (0 reviews) • Active installs 100
Unique Field Guard For ACF
Rating 0.0/5 (0 reviews) • Active installs 10
Security Made Easy
Rating 0.0/5 (0 reviews) • Active installs 0
Description
This plugin will warn you if you’re using or installing a knew as vulnerable extension or removed from official repository, a security must have plugin!
This uncludes a list of a maximum knew plugins to be vulnerable to any web security flaw, and also a list of more than 10.4k plugins removed from repo.
Just install it, it’s done, you’re warned in live!
Installation
- Extract the plugin folder from the downloaded ZIP file.
- Upload BAW WPSC folder to your /wp-content/plugins/ directory.
- Activate the plugin from the “Plugins” page in your Dashboard.
Frequently Asked Questions
- What can i do if a plugin is vulnerable!?
-> First you can read the exploit post, some solution can be provided, and most of the time : the desactivation or deletion is the only solution …
Review feed
No reviews available
Changelog
2.2.1
- 13 dec 2013
- Plugins list updated
2.2.0
- 28 sep 2013
- Notice will appear only on plugins list, not all plugins pages
2.1.0
- 18 sep 2013
- Notice Fix
2.0.0
- 18 sep 2013
- Full redone
- No more api keys
- No more ajax calls
- Included a 10.4k list of removed plugins from repo
- Included a list of knew as vulnerable plugin, this list will be updated montly
1.0
- 17 feb 2011
- First Release

