Report an error Security & Risk Analysis

wordpress.org/plugins/report-an-error

With this plugin visitors will be able to report typos or mistakes seen on your websites.

50 active installs v1.0.1 PHP + WP 3.3+ Updated Nov 26, 2015
%d0%be%d0%bf%d0%b5%d1%87%d0%b0%d1%82%d0%ba%d0%b0errorreporttypowidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Report an error Safe to Use in 2026?

Generally Safe

Score 85/100

Report an error has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The "report-an-error" plugin v1.0.1 presents a mixed security profile. On the positive side, the plugin boasts a very small attack surface with no apparent AJAX handlers, REST API routes, shortcodes, or cron events. Furthermore, all identified SQL queries utilize prepared statements, and there are no recorded vulnerabilities in its history, suggesting a potentially stable and well-maintained codebase. However, significant concerns arise from the static analysis. The presence of the `create_function` construct is a notable risk, as it can lead to remote code execution if not handled with extreme care and strict input validation, which is not evident from the analysis. Additionally, the relatively low percentage of properly escaped output (37%) indicates a high risk of cross-site scripting (XSS) vulnerabilities, allowing attackers to inject malicious scripts into the website. The complete absence of nonce checks and capability checks on any entry points, although the attack surface is currently zero, means that if any new entry points are added without proper security, they would be immediately vulnerable. While the plugin has no known CVEs, the internal code quality issues, particularly `create_function` and insufficient output escaping, are significant internal weaknesses that could be exploited.

Key Concerns

  • Use of create_function
  • Low percentage of proper output escaping
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Report an error Security Vulnerabilities

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

Report an error Code Analysis

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

Dangerous Functions Found

create_functionadd_action( 'widgets_init', create_function( '', 'register_widget( "Report_an_Error" );' ) );report-an-error.php:18

Output Escaping

37% escaped30 total outputs
Attack Surface

Report an error Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionadmin_menuinc\class.main.php:8
actionwp_footerinc\class.main.php:11
actionadmin_initreport-an-error.php:17
actionwidgets_initreport-an-error.php:18
actioninitreport-an-error.php:20
filterquery_varsreport-an-error.php:36
actiontemplate_redirectreport-an-error.php:42
Maintenance & Trust

Report an error Maintenance & Trust

Maintenance Signals

WordPress version tested4.4.34
Last updatedNov 26, 2015
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs50
Developer Profile

Report an error Developer Profile

ortox

3 plugins · 80 total installs

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

How We Detect Report an error

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/report-an-error/inc/class.main.php/wp-content/plugins/report-an-error/inc/class.widget.php
Script Paths
/wp-content/plugins/report-an-error/report-an-error.php

HTML / DOM Fingerprints

CSS Classes
RERR
Data Attributes
id="RERR"id="rerr_selected"id="rerr_message"
JS Globals
RERRRERR_seRERR_gsRERR_smRERR_sepost_error
REST Endpoints
/wp-json/report-an-error/send
FAQ

Frequently Asked Questions about Report an error