Below are the results of the most recent time the plugins Jetpack and Jetpack were graded through the Plugin Security Scorecard.
Checked on November 24, 2024Grade for Jetpack:
Issues the Plugin's Developer Should Address:
- The function filter_var() is used with the FILTER_DEFAULT filter, which doesn't do any filtering.
- The function filter_var() is used without a filter, so it doesn't do any filtering.
- The PHP function filter_input() is used without a filter, so it doesn't do any filtering.
- The plugin is using the WordPress function maybe_unserialize(), which is missing PHP's feature to protect against PHP object injection. A Core Committer of WordPress indicated that the it would not be a good idea for plugins to be using the function.
- 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 developer is redirecting those trying to report security issues to a third-party vulnerability bug bounty platform. That removes the ability to properly report many security issues to the developer. It is important for developers to have their own mechanism for addressing security issues. The European Union's Cyber Resilience Act will require developers to provide a direct contact.
- 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.
View the rest of the scorecard for Jetpack.
Checked on August 11, 2024Grade for Jetpack Protect:
Issues the Plugin's Developer Should Address:
- The function filter_var() is used without a filter, so it doesn't do any filtering.
- 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 developer is redirecting those trying to report security issues to a third-party vulnerability bug bounty platform. That removes the ability to properly report many security issues to the developer. It is important for developers to have their own mechanism for addressing security issues. The European Union's Cyber Resilience Act will require developers to provide a direct contact.
- 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.
View the rest of the scorecard for Jetpack Protect.
Highest Graded WordPress Plugin Vulnerability Data Plugins
Patchstack D+
WPScan D+
WPVulnerability D+
NinjaFirewall (WP Edition) D
Really Simple Security D
Solid Security F
MalCare WordPress Security Plugin F
Security Ninja F
Wordfence Security F
WP Encryption F
Highest Graded Brute Force Protection Plugins
Imporant Note: Brute force attacks are not happening, so you don't need a plugin that provides this type of protection.
Admin and Site Enhancements (ASE) C+
Limit Login Attempts Reloaded C+
Mythic Cerberus C+
Headers Security Advanced & HSTS WP C
Limit Login Attempts C
Titan Anti-spam & Security D+
Login Lockdown D+
WP Hide & Security Enhancer D+
Anti-Malware Security and Brute-Force Firewall D
WP Ghost (Hide My WP Ghost) D
Highest Graded All-In-One Security Plugins
Titan Anti-spam & Security D+
WP Ghost (Hide My WP Ghost) D
Really Simple Security D
All-In-One Security (AIOS) F
Solid Security F
BulletProof Security F
Defender Security F
MalCare WordPress Security Plugin F
SecuPress Free F
Security Optimizer F
Highest Graded Security Plugins
GD Security Headers B
HTTP Headers B
Malcure Malware Scanner B
Blackhole for Bad Bots C+
Limit Login Attempts Reloaded C+
Magic Login C+
Mythic Cerberus C+
Jetpack VaultPress C+
Headers Security Advanced & HSTS WP C
Limit Login Attempts C
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.
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.