Grade:
Issues the Plugin's Developer Should Address:
- The plugin contains a version of the third-party library jQuery UI that the developer of the library says has a vulnerability labeled as "XSS when refreshing a checkboxradio with an HTML-like initial text label". The plugin could be vulnerable due to that.
- The PHP function filter_input() is used without a filter, so it doesn't do any filtering.
- This plugin may use the function create_function(). That function has security risk due to using the function eval(). It had been deprecated as of PHP 7.2 and removed in PHP 8.0. According to the PHP documentation "Relying on this function is highly discouraged."
- The plugin doesn't contain a security.txt file (or alternatively a SECURITY.md or SECURITY-INSIGHTS.yml), which would provide information on how to report security issues to the developer.
- The plugin isn't listing in a security.txt file where the results of a security review that has been done of the plugin can be found. A well done security review would provide a good measure of the security of the plugin at the time it was done.
- The plugin isn't listing in a security.txt file where a software bill of materials (SBOM), which provides information on what third-party software is included in the plugin, can be found. That limits the ability to access the security of that third-party software.
- The plugin blocked less than half of the exploit attempts from the Plugin Vulnerabilities Firewall regression testing suite the last time the plugin was tested, so it missing a lot of the protection it could, and another plugin is, offering.
- The plugin is being marketed with a strong claim (or claims) of efficacy without citing evidence that backs up the claim.
- The plugin isn't providing a warning that its information on vulnerabilities in WordPress plugins is unreliable because it comes from a source known not to properly vet the information. That lack of vetting can lead to situations where a "fixed" vulnerabilty is subsequently widely exploited because there wasn't really a fix.
- The plugin is spreading misleading information about brute force attacks against WordPress websites, which are not actually happening, and causing the WordPress community to not focus on real security threats.
- The developer of this plugin is making a strong claim as to their handling of the security of their plugins without citing evidence that backs up that claim.
Resolving those issues would bring the plugin's grade up to an A+. You can notify the developer of the issues here. If the developer is interested in resolving those issues, we would be happy to help them to get started doing that.
You can also can consider using a similar plugin that is already more secure or one where the developer is interested in making their plugin more secure.
Additional Security Information
- Price for security review of version 2.152 of the plugin by Plugin Vulnerabilities: $800 USD
(Paying customers of the Plugin Vulnerabilities service select plugins to receive free reviews.)
Libraries Detected in Plugin
- Chart.js
- Version in Plugin: 4.1.2
- Latest Version of Library: 4.4.8
- This library's repository on GitHub doesn't have a security policy.
- OpenSSF Scorecard results (?)
- jQuery UI
- Version in Plugin: 1.13.1
- Latest Version of Library: 1.14.1
- This library is included in WordPress.
- OpenSSF Scorecard results (?)
Plugin Information
- Slug: security-malware-firewall
- Version: 2.152
- WordPress Plugin Directory listing
Highest Graded WordPress Plugin Vulnerability Data Plugins
WPVulnerability D+
Jetpack Protect D
NinjaFirewall (WP Edition) D
Patchstack D
Really Simple Security D
Solid Security F
Jetpack F
MalCare WordPress Security Plugin F
Security Ninja F
Wordfence Security F
Grades for Other CleanTalk Plugins
Share Scored Results for Security & Malware scan by CleanTalk
Check Another Plugin
Check Plugin Not in WordPress Plugin Directory
Subscribers of our service can submit ZIP files of plugins that are not in the WordPress Plugin Directory to have them checked. (Not all issues can be checked for with uploaded plugins, as they require data not available with just the plugin's files.) You can sign up for the service for free here. For existing subscribers, once you are logged in to your account, return to this page to access that functionality.
The results of these gradings will not be stored.
About the Scorecard
The Plugin Security Scorecard grades plugins' handling of security based on data coming from the Plugin Vulnerabilities service, checking over the contents of the plugin, the WordPress.org API, and data generated specifically for the tool. It provides a useful, but incomplete, understanding of the security posture of the plugin and its developer. All the issues identified are ones that the developer of the plugin has the ability to address to get the grade of the plugin up to an A+.
Grades are calculated based on issues with any of the following:
- Plugins known to be vulnerable
- Plugin developers with track records of improperly handling security problems
- Security issues in the plugin that can be detected in an automated fashion
- Issues with the developer's developerment processes that suggest that their could be problems with security
- Plugins making unsupported, misleading, and false claims about their handling of security and the handling of security with WordPress
We are working to expand and refine the tools' ability to provide a good measure of plugins' security status. If you are aware of an additional security concern with this plugin that isn't represented here, please contact us. Other feedback on the tool is also welcome.
If you want a comprehensive understanding of the security of the plugin, a well-done security review is really needed to provide that.