Custom Logs Security & Risk Analysis

wordpress.org/plugins/custom-logs

A sleek, modern plugin to manage WordPress debug logs with custom directories, levels, and advanced AJAX filtering.

10 active installs v1.1 PHP 7.4+ WP 4.8+ Updated May 27, 2025
admin-toolsdebuglogginglogswordpress-debug
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Custom Logs Safe to Use in 2026?

Generally Safe

Score 100/100

Custom Logs has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11mo ago
Risk Assessment

The "custom-logs" v1.1 plugin exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, 100% proper output escaping, and 100% use of prepared statements for SQL queries are significant strengths. The presence of numerous nonce and capability checks across its entry points indicates a good understanding of WordPress security best practices, further reinforced by the lack of any recorded vulnerabilities or CVEs in its history. This suggests a well-maintained and secure codebase.

While the static analysis reveals no critical or high severity issues, including unsanitized paths in taint flows, the presence of file operations (13 instances) warrants a brief mention. Although no specific risks are identified in the current analysis, operations involving file system access can sometimes be vectors for more complex attacks if not meticulously handled in all scenarios. However, given the other positive indicators, this remains a minor point of observation rather than a concrete concern at this version.

In conclusion, "custom-logs" v1.1 appears to be a secure plugin. Its adherence to core WordPress security principles, coupled with a clean vulnerability history, suggests a low risk for most WordPress installations. The plugin developers have demonstrated a commendable effort in securing their code.

Vulnerabilities
None known

Custom Logs Security Vulnerabilities

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

Custom Logs Release Timeline

v1.0
Code Analysis
Analyzed Apr 16, 2026

Custom Logs Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
0
267 escaped
Nonce Checks
21
Capability Checks
2
File Operations
13
External Requests
0
Bundled Libraries
0

Output Escaping

100% escaped267 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

3 flows
customdebug_log_file_page (custom-debug-logs.php:408)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Custom Logs Attack Surface

Entry Points4
Unprotected0

AJAX Handlers 4

authwp_ajax_customdebug_get_file_mtimecustom-debug-logs.php:351
authwp_ajax_customdebug_filter_logscustom-debug-logs.php:406
authwp_ajax_customdebug_filter_logscustom-debug-logs.php:1114
authwp_ajax_download_log_filecustom-debug-logs.php:1148
WordPress Hooks 4
filtercustomdebug_log_errorcustom-debug-logs.php:207
actionmuplugins_loadedcustom-debug-logs.php:236
actionadmin_menucustom-debug-logs.php:238
actionadmin_enqueue_scriptscustom-debug-logs.php:251
Maintenance & Trust

Custom Logs Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedMay 27, 2025
PHP min version7.4
Downloads475

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Custom Logs Developer Profile

Byron Jacobs

1 plugin · 10 total installs

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

How We Detect Custom Logs

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Custom Logs