WPScan WordPress Security Scanner - Scans your system for security vulnerabilities listed in the WPScan Vulnerability Database.
Prioritized issue groups from the latest Plugin Check scan
Security
319
11 issue groups
Maintainability
229
12 issue groups
I18n
198
2 issue groups
Sample message
Mismatched text domain. Expected 'wpscan' but got 'action-scheduler'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"' value='$api_token' class='blur-on-lose-focus regular-text' $disabled>"'.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"The bulk action $action does not have a callback method"'.
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
rand() is discouraged. Use the far less predictable wp_rand() instead.
Sample message
Use placeholders and $wpdb->prepare(); found $column
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
Processing form data without nonce verification.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$all_user_ids".
Sample message
Detected usage of a non-sanitized input variable: $_GET['ID']
Sample message
$_GET['ID'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Function "wp_json_encode()" requires WordPress 4.1.0, but your plugin minimum supported version is WordPress 3.4.0.
Sample message
Unescaped parameter $query used in $wpdb->get_var()\n$query assigned unsafely at line 260.
Sample message
Using date_default_timezone_set() and similar isn't allowed, instead use WP internal timezone support.
Sample message
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "as_enqueue_async_action".
Sample message
Use placeholders and $wpdb->prepare(); found interpolated variable $column at "`$column` = %s"
Sample message
Detected usage of a possibly undefined superglobal array index: $_REQUEST['nonce']. Check that the array index exists before using it.
Sample message
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "BatchFetcher_Test".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WPLANG".
Not analyzed yet.
First score snapshot
v1.16
21
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 21 | 792 | 527 | 265 | v1.16 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.