hiWeb Upload Dir Limit Security & Risk Analysis

wordpress.org/plugins/hiweb-upload-dir-limit

This little plugin allows you to specify a size limit upload folder.

10 active installs v1.0.0.0 PHP + WP 4.1+ Updated May 21, 2016
dir-limitfolder-limitsize-limitstop-uploadupload-limit
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is hiWeb Upload Dir Limit Safe to Use in 2026?

Generally Safe

Score 85/100

hiWeb Upload Dir Limit has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9yr ago
Risk Assessment

The "hiweb-upload-dir-limit" plugin v1.0.0.0 presents a seemingly strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the plugin's attack surface. Furthermore, the code analysis shows no dangerous functions, no SQL queries that are not prepared, and no direct file operations or external HTTP requests. This indicates a cautious approach to development in these critical areas.

However, the lack of any capability checks or nonce checks on the zero identified entry points is a significant concern. While there are no entry points detected, if any were to be introduced in future versions or through other means, they would be entirely unprotected. The limited number of output strings, with one out of three not properly escaped, also presents a minor risk of cross-site scripting (XSS) vulnerabilities if that output were to contain user-supplied data.

The vulnerability history shows a complete absence of any known CVEs, which is a very positive indicator. This suggests that the plugin has either been exceptionally well-developed and audited, or it has not been a target for exploitation, potentially due to its limited functionality or attack surface. In conclusion, the plugin exhibits strengths in its minimal attack surface and secure handling of core web application functions. The primary weakness lies in the complete absence of authorization and nonces on any potential entry points, which, while currently not exploitable due to the lack of entry points, represents a latent risk.

Key Concerns

  • Missing capability checks on potential entry points
  • Missing nonce checks on potential entry points
  • Unescaped output detected
Vulnerabilities
None known

hiWeb Upload Dir Limit Security Vulnerabilities

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

hiWeb Upload Dir Limit Code Analysis

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

Output Escaping

67% escaped3 total outputs
Attack Surface

hiWeb Upload Dir Limit Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionadmin_menuinc\options-page.php:4
filterwp_handle_upload_prefilterinc\options-page.php:24
Maintenance & Trust

hiWeb Upload Dir Limit Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedMay 21, 2016
PHP min version
Downloads5K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

hiWeb Upload Dir Limit Developer Profile

Den Media

9 plugins · 100 total installs

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

How We Detect hiWeb Upload Dir Limit

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

Asset Fingerprints

Version Parameters
hiweb-upload-dir-limit/inc/

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about hiWeb Upload Dir Limit