Free daily vulnerability scans & WordPress security, powered by WPScan (an Automattic brand) and its 60,000+ vulnerability database. No setup needed!
Prioritized issue groups from the latest Plugin Check scan
I18n
592
1 issue group
Maintainability
188
17 issue groups
Security
92
5 issue groups
Performance
1
1 issue group
Sample message
Mismatched text domain. Expected 'jetpack-protect' but got 'jetpack-account-protection'.
Sample message
Use of a direct database call is discouraged.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"$errstr (file: $errfile; line: $errline)"'.
Sample message
Unescaped parameter $custom_table_name used in $wpdb->get_row()\n$custom_table_name assigned unsafely at line 614.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
Hook names invoked by a theme/plugin should start with the theme/plugin prefix. Found: "'jitm_' . $envelope->CTA->hook".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
The use of function ini_set() is discouraged
Sample message
Detected usage of meta_key, possible slow query.
Sample message
Detected usage of meta_value, possible slow query.
Sample message
error_log() found. Debug code should not normally be used in production.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$add_action".
Sample message
Processing form data without nonce verification.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "DISABLE_JETPACK_WAF".
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Jetpack Protect" - contains the restricted term "jetpack" and cannot be used to begin your plugin name. We disallow the use of certain terms in ways that are abused, or potentially infringe on and/or are misleading with regards to trademarks. You may use the term "jetpack" elsewhere in your plugin name, such as "... for jetpack".
Sample message
Processing form data without nonce verification.
Sample message
Plugin Updater detected. Detected code which may be altering WordPress update routines. Detected: _site_transient_update_plugins
Sample message
var_dump() found. Debug code should not normally be used in production.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"rule $rule_id - reason $reason"'.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
Using exclusionary parameters, like exclude, in calls to get_posts() should be done with caution, see https://wpvip.com/documentation/performance-improvements-by-removing-usage-of-post__not_in/ for more information.
Sample message
Tested up to: 6.9 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Sample message
Plugin Updater detected. These are not permitted in WordPress.org hosted plugins. Detected: site_transient_update_plugins
Not analyzed yet.
First score snapshot
v5.0.0
30
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 30 | 874 | 657 | 217 | v5.0.0 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.