sHub-Log Security & Risk Analysis

wordpress.org/plugins/syntaxhub-securelog

Records suspicious login attempts, 404s, and malicious requests, then blocks IPs after repeated attempts.

10 active installs v1.2.11 PHP 7.2+ WP 5.0+ Updated Jul 20, 2026
attack-logip-blockingprotectionsecurity
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is sHub-Log Safe to Use in 2026?

Generally Safe

Score 100/100

sHub-Log has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The syntaxhub-securelog plugin, version 1.0.3, exhibits a generally strong security posture with several good practices in place. The complete absence of external HTTP requests, file operations, and SQL queries not using prepared statements are significant strengths. The plugin also demonstrates a low attack surface with no reported AJAX handlers, REST API routes, shortcodes, or cron events exposed without authentication. Furthermore, the output escaping is nearly perfect, and nonce and capability checks are present on all identified entry points. However, the taint analysis reveals a concerning number of flows with unsanitized paths. While no critical or high severity taint flows were identified, the presence of three such flows with high severity indicates a potential for information disclosure or unauthorized access if not addressed properly. The plugin's vulnerability history is clean, with no known CVEs, which is a positive indicator of its past security. Despite this, the taint analysis findings warrant careful investigation and remediation to ensure the plugin remains secure.

Key Concerns

  • High severity unsanitized paths in taint analysis
Vulnerabilities
None known

sHub-Log Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

sHub-Log Release Timeline

v1.2.11Current
v1.2.10
v1.2.9
v1.2.8
v1.2.7
v1.2.6
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.9
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.0
Code Analysis
Analyzed Apr 16, 2026

sHub-Log Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
12 prepared
Unescaped Output
1
48 escaped
Nonce Checks
2
Capability Checks
2
File Operations
0
External Requests
0
Bundled Libraries
0

SQL Query Safety

100% prepared12 total queries

Output Escaping

98% escaped49 total outputs
Data Flows · Security
3 unsanitized

Data Flow Analysis

5 flows3 with unsanitized paths
syntaxhub_securelog_unblock_ip_address (SyntaxHub-SecureLog.php:310)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

sHub-Log Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionwp_login_failedSyntaxHub-SecureLog.php:71
actionlogin_initSyntaxHub-SecureLog.php:151
actionadmin_menuSyntaxHub-SecureLog.php:165
actionadmin_enqueue_scriptsSyntaxHub-SecureLog.php:190
actionadmin_initSyntaxHub-SecureLog.php:283
Maintenance & Trust

sHub-Log Maintenance & Trust

Maintenance Signals

WordPress version tested7.0.2
Last updatedJul 20, 2026
PHP min version7.2
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

sHub-Log Developer Profile

SyntaxCloud

2 plugins · 20 total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect sHub-Log

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/syntaxhub-securelog/js/admin.js
Script Paths
/wp-content/plugins/syntaxhub-securelog/js/admin.js
Version Parameters
syntaxhub-securelog/js/admin.js?ver=1.0.3

HTML / DOM Fingerprints

JS Globals
syntaxhubSecurelogAdmin
FAQ

Frequently Asked Questions about sHub-Log