LogMate Security & Risk Analysis

wordpress.org/plugins/logmate

Modern log management and export for WordPress with purging, filtering, and export. by BruteFort

0 active installs v1.0.0 PHP 7.4+ WP 5.0+ Updated Feb 16, 2026
debugdevelopererrorsexportlogging
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is LogMate Safe to Use in 2026?

Generally Safe

Score 100/100

LogMate 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 plugin "logmate" v1.0.0 demonstrates a strong security posture with no known CVEs and a complete absence of critical or high-severity findings in the static and taint analysis. The code adheres to good security practices by utilizing prepared statements for all SQL queries, implementing nonce checks, and performing capability checks for its limited entry points. The high percentage of properly escaped output further indicates a diligent approach to preventing cross-site scripting vulnerabilities. The plugin's attack surface is minimal, with no apparent AJAX handlers, REST API routes, shortcodes, or cron events, significantly reducing the potential for unauthorized access or manipulation. The single flow with an unsanitized path, while not flagged as critical or high severity, warrants attention as it represents a potential area for improvement in input validation, particularly if it involves file operations. Overall, "logmate" v1.0.0 appears to be a securely developed plugin, with its vulnerability history being completely clear, suggesting a commitment to security by its developers.

Key Concerns

  • Flow with unsanitized path detected
Vulnerabilities
None known

LogMate Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 17, 2026

LogMate Code Analysis

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

Output Escaping

94% escaped17 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
create_log_file (includes\Settings.php:291)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

LogMate Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionrest_api_initincludes\Routes\Routes.php:24
actionadmin_menuincludes\Settings.php:23
actionadmin_enqueue_scriptsincludes\Settings.php:24
actionwp_enqueue_scriptsincludes\Settings.php:25
actionadmin_initincludes\Settings.php:26
filterdoing_it_wrong_trigger_errorlogmate.php:66
actioninitlogmate.php:156
Maintenance & Trust

LogMate Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 16, 2026
PHP min version7.4
Downloads136

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

LogMate Developer Profile

Yoyal Limbu

2 plugins · 0 total installs

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

How We Detect LogMate

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/logmate/dist/assets/index.js/wp-content/plugins/logmate/dist/assets/vendor.js
Script Paths
/wp-content/plugins/logmate/dist/assets/index.js/wp-content/plugins/logmate/dist/assets/vendor.js
Version Parameters
logmate/dist/assets/index.js?ver=logmate/dist/assets/vendor.js?ver=

HTML / DOM Fingerprints

CSS Classes
logmate-admin-app
Data Attributes
data-logmate-urldata-logmate-nonce
JS Globals
logmate_vars
REST Endpoints
/wp-json/logmate/
FAQ

Frequently Asked Questions about LogMate