View WP Error Log Security & Risk Analysis

wordpress.org/plugins/view-wp-error-log

Easy Wordpress Error Logs

10 active installs v3.1 PHP + WP 3.3+ Updated Oct 28, 2014
errorlog
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is View WP Error Log Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The "view-wp-error-log" plugin version 3.1 exhibits a mixed security posture. While it has a clean vulnerability history with no known CVEs, the static analysis reveals several concerning practices. Notably, the absence of any output escaping on the single output identified is a significant weakness, potentially leading to cross-site scripting (XSS) vulnerabilities if any dynamic data is displayed. Furthermore, the presence of two unsanitized path flows in the taint analysis, even without critical or high severity, suggests a risk of arbitrary file access or manipulation if these flows are exposed to user input. The complete lack of nonce checks and capability checks across all entry points, combined with file operations, also raises flags. Although the attack surface is currently zero, the potential for exploitation exists due to these unmitigated risks. The plugin's strengths lie in its avoidance of dangerous functions and the use of prepared statements for any SQL queries, but these are overshadowed by the identified output and path sanitization issues.

Key Concerns

  • Unescaped output found
  • Unsanitized paths in taint flows
  • No nonce checks on entry points
  • No capability checks on entry points
  • File operations without evident sanitization
Vulnerabilities
None known

View WP Error Log Security Vulnerabilities

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

View WP Error Log Release Timeline

v3.1Current
v3.0
v2.3
v2.2
v2.1
v2.0
v1.0
Code Analysis
Analyzed Mar 16, 2026

View WP Error Log Code Analysis

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

Output Escaping

0% escaped1 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
updateAction (admin\controllers\wp-error-log-controller.php:7)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

View WP Error Log Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_initview-wp-error-log.php:36
actionadmin_menuview-wp-error-log.php:41
actionwpview-wp-error-log.php:66
actionview_wp_error_log_daily_eventview-wp-error-log.php:77

Scheduled Events 1

view_wp_error_log_daily_event
Maintenance & Trust

View WP Error Log Maintenance & Trust

Maintenance Signals

WordPress version tested4.0.38
Last updatedOct 28, 2014
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

View WP Error Log Developer Profile

MMDeveloper

7 plugins · 2K total installs

69
trust score
Avg Security Score
85/100
Avg Patch Time
2139 days
View full developer profile
Detection Fingerprints

How We Detect View WP Error Log

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/view-wp-error-log/admin/pages/css/wp-error-log.css/wp-content/plugins/view-wp-error-log/admin/pages/js/wp-error-log.js

HTML / DOM Fingerprints

CSS Classes
wp-error-log-pageerror-log-tablecode
Data Attributes
data-log-filedata-log-lines
JS Globals
wp_error_log_ajax_object
FAQ

Frequently Asked Questions about View WP Error Log