Restrict WooCommerce Reports Status Security & Risk Analysis

wordpress.org/plugins/restrict-woocommerce-reports-status

Make WooCommerce consider only "Completed" and "Processing" status for reports, not "On Hold"

10 active installs v1.0.0 PHP 5.6+ WP 4.0+ Updated May 12, 2018
reportswoocommercewoocommerce-reports
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Restrict WooCommerce Reports Status Safe to Use in 2026?

Generally Safe

Score 85/100

Restrict WooCommerce Reports Status has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 8yr ago
Risk Assessment

The "restrict-woocommerce-reports-status" plugin v1.0.0 exhibits an exceptionally strong security posture based on the provided static analysis and vulnerability history. The code analysis reveals a complete absence of dangerous functions, external HTTP requests, file operations, and SQL queries that are not properly prepared. Furthermore, all identified SQL queries utilize prepared statements, and there are no instances of unescaped output or file operations, indicating robust data handling practices. The plugin also appears to have no known vulnerabilities, with zero CVEs recorded, and no history of past security issues. This clean record suggests diligent development and a focus on secure coding principles.

While the plugin demonstrates excellent security practices, the complete lack of an attack surface (AJAX handlers, REST API routes, shortcodes, cron events) and the absence of any taint flows, while beneficial for security, also means the plugin may have very limited functionality. The score is currently at 100 due to the absence of any negative indicators, but it is worth noting that a truly feature-rich plugin would likely have some entry points and potentially require more robust security checks. However, based solely on the provided data, this plugin appears to be highly secure.

Vulnerabilities
None known

Restrict WooCommerce Reports Status Security Vulnerabilities

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

Restrict WooCommerce Reports Status Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

Restrict WooCommerce Reports Status Code Analysis

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

Restrict WooCommerce Reports Status Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitrestrict-woocommerce-reports-status.php:46
filterwoocommerce_reports_order_statusesrestrict-woocommerce-reports-status.php:49
actionplugins_loadedrestrict-woocommerce-reports-status.php:80
Maintenance & Trust

Restrict WooCommerce Reports Status Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedMay 12, 2018
PHP min version5.6
Downloads1K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Restrict WooCommerce Reports Status Developer Profile

Fernando Acosta

8 plugins · 109K total installs

92
trust score
Avg Security Score
89/100
Avg Patch Time
5 days
View full developer profile
Detection Fingerprints

How We Detect Restrict WooCommerce Reports Status

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 Restrict WooCommerce Reports Status