Execute arbitrary SQL queries against your WordPress database from the Admin.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
25
13 issue groups
Security
7
4 issue groups
Repo Compliance
3
3 issue groups
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$link_template".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '$links'.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_query.
Sample message
Processing form data without nonce verification.
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_affected_rows.
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_connect.
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_error.
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_fetch_array.
Sample message
Accessing the database directly should be avoided. Please use the $wpdb object and associated functions instead. Found: mysqli_fetch_assoc.
Sample message
Detected usage of a non-sanitized input variable: $_POST['sql']
Sample message
$_POST['sql'] not unslashed before sanitization. Use wp_unslash() or similar
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
screen_icon() has been deprecated since WordPress version 3.8.0.
Sample message
In footer ($in_footer) is not set explicitly wp_register_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
Tested up to: 4.6 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
One or more tags were ignored. Please limit your plugin to 5 tags.
Sample message
Incorrect Stable Tag. It's recommended not to use "Stable Tag: trunk". Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org.
Not analyzed yet.
First score snapshot
v1.4
70
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 70 | 35 | 18 | 17 | v1.4 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.