WP Automatic Video Player ReSize Security & Risk Analysis

wordpress.org/plugins/wp-automatic-video-player-resize

WordPress automatic video player resize(Youtube,VK,Mail.ru vsvs)

10 active installs v1.0 PHP + WP 2.9+ Updated Sep 25, 2015
widgetwordpreswordpress-automatic-resizewordpress-automatic-size
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Automatic Video Player ReSize Safe to Use in 2026?

Generally Safe

Score 85/100

WP Automatic Video Player ReSize 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 "wp-automatic-video-player-resize" plugin v1.0 presents a mixed security profile. On the positive side, it demonstrates good practices by having no known CVEs and no bundled libraries, indicating a lean and potentially well-maintained codebase. The absence of dangerous functions, file operations, and external HTTP requests further reduces common attack vectors. However, several concerns emerge from the static analysis. The complete lack of nonce checks and capability checks across all entry points is a significant weakness, meaning any functionality exposed could potentially be exploited by unauthenticated users or users with insufficient privileges. Furthermore, the taint analysis revealing "flows with unsanitized paths" is worrying, even without critical or high severity findings, as it suggests potential for unexpected behavior or data manipulation if an attacker can influence the input to these flows. The proper escaping of only 40% of outputs also introduces a risk of cross-site scripting (XSS) vulnerabilities.

Key Concerns

  • No capability checks on entry points
  • No nonce checks on entry points
  • Taint flows with unsanitized paths
  • Low percentage of properly escaped output
Vulnerabilities
None known

WP Automatic Video Player ReSize Security Vulnerabilities

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

WP Automatic Video Player ReSize Release Timeline

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

WP Automatic Video Player ReSize Code Analysis

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

Output Escaping

40% escaped5 total outputs
Data Flows · Security
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
WpAJANS_resize_video_PLAYER_manager_page (index.php:19)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

WP Automatic Video Player ReSize Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menuindex.php:12
filterthe_contentindex.php:56
filterthe_excerptindex.php:57
Maintenance & Trust

WP Automatic Video Player ReSize Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedSep 25, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP Automatic Video Player ReSize Developer Profile

Mustafa KUCUK

8 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 WP Automatic Video Player ReSize

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
updated
Data Attributes
id="video-player-width"name="video-player-width"id="video-player-height"name="video-player-height"id="hiddenoption"name="hiddenoption"
FAQ

Frequently Asked Questions about WP Automatic Video Player ReSize