Resize on Upload Security & Risk Analysis

wordpress.org/plugins/resize-on-upload

Provides the ability to set a maximum width or height an uploaded image can be, if the image is larger then it is resized.

100 active installs v1.0.1 PHP + WP 2.8.1+ Updated Aug 4, 2009
imagephotoresizeupload
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Resize on Upload Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 16yr ago
Risk Assessment

The 'resize-on-upload' plugin v1.0.1 exhibits a strong security posture in several key areas based on the provided static analysis. The absence of any known CVEs, critical taint flows, raw SQL queries, or significant attack surface points without authentication are all positive indicators. The plugin also demonstrates good practices by utilizing prepared statements for its SQL queries and performing at least one capability check. However, the analysis does reveal areas that warrant attention and contribute to a reduced security score. Specifically, the presence of unescaped output in 50% of detected output points presents a potential risk for cross-site scripting (XSS) vulnerabilities. While the attack surface is reported as zero, the file operations and lack of comprehensive input sanitization for these operations could be a vector if not handled carefully within the plugin's logic. The complete absence of nonce checks on any potential entry points is also a concern, as this is a fundamental WordPress security mechanism to prevent CSRF attacks.

Overall, while the plugin has a clean vulnerability history and avoids many common pitfalls, the unescaped output and lack of nonce checks represent exploitable weaknesses. The file operations, though limited, also require careful review to ensure they are not mishandled. The plugin's strengths lie in its controlled database interactions and lack of known historical issues, but its weaknesses in output sanitization and CSRF protection detract from its overall security. The 'no taint flows' signal is promising, but it's often dependent on the thoroughness of the analysis itself.

Key Concerns

  • Unescaped output detected
  • Missing nonce checks
Vulnerabilities
None known

Resize on Upload Security Vulnerabilities

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

Resize on Upload Code Analysis

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

Output Escaping

50% escaped4 total outputs
Attack Surface

Resize on Upload Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_handle_uploadresize-on-upload.php:107
actionadmin_menuresize-on-upload.php:109
Maintenance & Trust

Resize on Upload Maintenance & Trust

Maintenance Signals

WordPress version tested2.8.3
Last updatedAug 4, 2009
PHP min version
Downloads8K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

Resize on Upload Developer Profile

linal

1 plugin · 100 total installs

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

How We Detect Resize on Upload

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
fade-ff0000
Data Attributes
name="rou_max_width"name="rou_max_height"
FAQ

Frequently Asked Questions about Resize on Upload