Secure your WordPress site from brute-force attacks, threats, malware, and bots. Free to use and easy to set up.
Prioritized issue groups from the latest Plugin Check scan
Security
68
5 issue groups
Maintainability
53
17 issue groups
I18n
2
2 issue groups
Repo Compliance
1
1 issue group
Sample message
Detected usage of a non-sanitized input variable: $_COOKIE[$sg_2fa_user_cookie]
Sample message
$_COOKIE[$sg_2fa_user_cookie] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Detected usage of a possibly undefined superglobal array index: $_SERVER['HTTP_HOST']. Check that the array index exists before using it.
Sample message
Processing form data without nonce verification.
Sample message
Detected usage of meta_query, possible slow query.
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
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
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
parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.
Sample message
Stylesheets must be registered/enqueued via wp_enqueue_style()
Sample message
debug_backtrace() found. Debug code should not normally be used in production.
Sample message
error_reporting() can lead to full path disclosure.
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fputs().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().
Sample message
File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: is_writable().
Sample message
rand() is discouraged. Use the far less predictable wp_rand() instead.
Sample message
Missing $domain parameter in function call to __().
Sample message
The $text parameter must be a single text string literal. Found: $entry['visitor_type']
Sample message
Plugin name "Security Optimizer - The All-In-One Protection Plugin" is different from the name declared in plugin header "Security Optimizer".
Sample message
The "/vendor" directory using composer exists, but "composer.json" file is missing.
Sample message
The "Domain Path" header in the plugin file must point to an existing folder. Found: "languages"
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "Security Optimizer - The All-In-One Protection Plugin" - contains the restricted term "plugin" which cannot be used at all in your plugin name.
Potential connections found in static code analysis.
Outbound calls
48
External assets
3
Incoming endpoints
3
No public endpoints detected.
wp_ajax
wp_ajax
wp_ajax
4 score snapshots
v1.6.5
35
Latest
v1.6.4
35
Score
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 35 | 126 | 40 | 86 | v1.6.5 | 2.0.0 |
| 35 | 124 | 40 | 84 | v1.6.4 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.